Postgres Pro
Downloads
Home   >   mailing lists

Re: Problem Interval() and Timestamp() with Postgres 7.21 - Mailing list pgsql-php

From Christopher Kings-Lynne
Subject Re: Problem Interval() and Timestamp() with Postgres 7.21
Date
Msg-id GNELIHDDFBOCMGBFGEFOOEDHCDAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Problem Interval() and Timestamp() with Postgres 7.21  ("Peter" <peterh@600ml.com.au>)
List pgsql-php
Tree view
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

pgsql-php by date:

Previous
From: "Peter"
Date:
Subject: Problem Interval() and Timestamp() with Postgres 7.21
Next
From: ernhlegal_ins@juno.com
Date:
Subject: If you had a legal problem today, what would you do? fkqd