Problem Interval() and Timestamp() with Postgres 7.21

This is a multi-part message in MIME format.

------=_NextPart_000_0055_01C22F1A.24B4A970
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,



Has anyone expreience these problems with postgres 7.21??

timestamp('now') or interval('7 days') now result in parse errors when exec=
uted ????

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 po=
stgresql????

any help would be greately appreciated.



regards, Peter

------=_NextPart_000_0055_01C22F1A.24B4A970
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Re: Problem Interval() and Timestamp() with Postgres 7.21

This is a multi-part message in MIME format.

------=_NextPart_000_006D_01C22F0B.F6D9A680
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

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@postgresql.org
[mailto:pgsql-php-owner@postgresql.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

------=_NextPart_000_006D_01C22F0B.F6D9A680
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">

oma=20
size=3D2>-----Original Message-----
From:=20
pgsql-php-owner@postgresql.org [mailto:pgsql-php-owner@postgresql.org]=
On=20
Behalf Of Peter
Sent: Friday, 19 July 2002 9:48 AM
To=
:=20
PostgreSQL PHP
Subject: [PHP] Problem Interval() and Timestamp(=
)=20
with Postgres 7.21

Hello,

 

 

 

Has anyone expreience these problems wit=
h=20
postgres 7.21??

 

timestamp('now') or interval('7 days') n=
ow result=20
in parse errors when executed ????

 

this renders an import script of mine us=
eless,=20
when it was running without problems on previous versions?

 

have i compiled postgres wrong? has this=
=20
functionality been dropped from postgresql????

 

any help would be greately=20
appreciated.

 

 

 

regards,=20
Peter