Hmm, both these approaches seem to work for me on PostgreSQL 7.1.3 with the
newer 7.2 driver.
Using the {ts ...} syntax directly at psql will fail beacuse it's a
JDBC-specific escape.
-- Bill
----- Original Message -----
From: "Sam Joseph" <[EMAIL PROTECTED]>
To: "Turbine Torque Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, May 22, 2002 10:44 AM
Subject: Re: Fw: [PATCH] Postgresql date constraints
> Just to correct my previous email ....
>
> Sam Joseph wrote:
>
> > Bill Schneider wrote:
> >
> >> This patch is not necessary any more. It turned out that my PostgreSQL
> >> driver was stale (not by more than a few weeks, though!)
> >>
> >>
> > Updating my PostgreSQL driver does not seem to have fixed that issue
> > for me. In fact it would seem that I need to upgrade my version of
> > PostgreSQL.
>
> Actually I was assuming that was the problem. Updating to postgre 7.2.1
> does not allow the following kind of statement to operate:
>
> {ts '2002-05-22 21:40:36.906'}
>
> and the approach suggested in the PATCH
>
> TO_TIMESTAMP('2002-05-22 23:28:23', 'yyyy-mm-dd hh24:mi:ss' )
>
> also seems to fail.
>
> My apologies in advance as this is probably down to some oversight on my
> part, but I have been trying these both through the latest jdbc driver
> (7.2) and through the psql text interface ....
>
> CHEERS> SAM
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
