Skip site navigation (1) Skip section navigation (2)

Re: Bad timestamp external representation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Tessier <m_tessier(at)sympatico(dot)ca>
Cc: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>,pgsql-general(at)postgresql(dot)org
Subject: Re: Bad timestamp external representation
Date: 2003-04-29 04:02:20
Message-ID: 14238.1051588940@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Mark Tessier <m_tessier(at)sympatico(dot)ca> writes:
> Actually, that was the last thing I tried before I wrote this note. Before I entered

> herboris=> INSERT INTO cart (cartid, clientid, invdate, paydate) VALUES
> herboris-> (4469858, 2, 'current', 'now');
> And still got the same error message:
> ERROR:  Bad date external representation 'current'

'now' is the only accepted spelling.

('current' used to mean something subtly different from 'now', but that
meaning isn't supported anymore.)

			regards, tom lane


In response to

Responses

pgsql-general by date

Next:From: Benjamin ScherreyDate: 2003-04-29 04:29:44
Subject: Re: Bug(?) with cursors using aggregate functions.
Previous:From: Tom LaneDate: 2003-04-29 03:51:51
Subject: Re: Bug(?) with cursors using aggregate functions.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group