Re: 'current' timestamp chokes jdbc driver

From: Joseph Shraibman <jks(at)selectacast(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'pgsql-jdbc(at)postgresql(dot)org'" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: 'current' timestamp chokes jdbc driver
Date: 2001-05-08 00:06:27
Message-ID: 3AF73883.84A6DF28@selectacast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Tom Lane wrote:
>
> Joseph Shraibman <jks(at)selectacast(dot)net> writes:
> > If you set a timestamp field to be 'current' as per
> > http://www.ca.postgresql.org/docs/postgres/datatype-datetime.html#AEN322
> > jdbc chokes on selecting that value:
>
> 'current' is deprecated and is going to go away in 7.2 anyway (that's
> why it's undocumented). So I'm not sure it's worth hacking JDBC to
> deal with it...
>

As long as it is there jdbc should be able to handle it w/o throwing an
Exception, and the jdbc drivers are expected to connect with old
versions of the database so it makes sense to leave the handling in
there permanently (but maybe with a comment).

And 'current' *is* documented, I gave the url above.

--
Joseph Shraibman
jks(at)selectacast(dot)net
Increase signal to noise ratio. http://www.targabot.com

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Bruce Momjian 2001-05-08 00:10:39 Re: A Bug Fix - Is this a real bug? Has this already been fixed?
Previous Message Tom Lane 2001-05-07 23:51:28 Re: 'current' timestamp chokes jdbc driver