| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Perl DBI and placeheld values |
| Date: | 2003-01-30 14:41:02 |
| Message-ID: | 20030130144102.GB32517@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 29, 2003 at 22:30:49 +0000,
"Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> wrote:
>
> So just how do others manage this situation without resorting to special casing
> everything?
In this particular case you could use 'now' instead of current_timestamp.
In some other cases you might be able to use default to use the default
value.
In general you probably want two different sql statements and not try
to mix constant data and function calls in the same prepared statement.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick Bye (WFF) | 2003-01-30 15:07:50 | Re: Problem starting postmaster at startup |
| Previous Message | Erwin Moller | 2003-01-30 14:03:29 | Postgresql7.3: after dropping a column a .............pg.dropped............ column exists |