From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Peter" <peterh(at)600ml(dot)com(dot)au>, "PostgreSQL PHP" <pgsql-php(at)postgresql(dot)org> |
Subject: | Re: Problem Interval() and Timestamp() with Postgres 7.21 |
Date: | 2002-07-19 02:06:35 |
Message-ID: | GNELIHDDFBOCMGBFGEFOOEDHCDAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php |
The timestamp() syntax has been modified, so be compliant with SQL99. (eg.
timestamp(4) for 4 digits of millisecond precision). It's in the release
notes.
So, you will now need to double quote and it will work fine:
"timestamp"('now') and "interval"('7 days');
However I suggest you just convert to standard syntax:
select timestamp 'now';
or better: select current_timestamp;
and
select interval '7 days';
These are sql99 compatible statements...
Chris
-----Original Message-----
From: pgsql-php-owner(at)postgresql(dot)org
[mailto:pgsql-php-owner(at)postgresql(dot)org]On Behalf Of Peter
Sent: Friday, 19 July 2002 9:48 AM
To: PostgreSQL PHP
Subject: [PHP] Problem Interval() and Timestamp() with Postgres 7.21
Hello,
Has anyone expreience these problems with postgres 7.21??
timestamp('now') or interval('7 days') now result in parse errors when
executed ????
this renders an import script of mine useless, when it was running without
problems on previous versions?
have i compiled postgres wrong? has this functionality been dropped from
postgresql????
any help would be greately appreciated.
regards, Peter
From | Date | Subject | |
---|---|---|---|
Next Message | 2002-07-20 19:41:50 | If you had a legal problem today, what would you do? fkqd | |
Previous Message | Peter | 2002-07-19 01:48:05 | Problem Interval() and Timestamp() with Postgres 7.21 |