From: | Barry Lind <barry(at)xythos(dot)com> |
---|---|
To: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
Cc: | Peter Kovacs <peter(dot)kovacs(at)sysdata(dot)siemens(dot)hu>, pgsql-general(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: [JDBC] Prepared statement performance... |
Date: | 2002-09-27 19:14:19 |
Message-ID: | 3D94AE0B.2000200@xythos.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
Dimtry,
Dmitry Tkach wrote:
> Not realy... You should not be required to know about postgres date
> format, as long as it matches Timestamp.toString () output (and it
> currently does), and I
> see no reason why it would not (you just need to make sure that the
> client and the server are in the same locale, but that's a different
> discussion, because whatever
> JDBC does in setTimestamp () would locale-dependent anyway).
This certainly isn't true for all databases. Oracle for example where
the database format for dates is DD-MON-YY which is very different from
the Timestamp.toString() method. And actually the postgres format is
different and incompatible with javas format when you start having to
deal with timezone information.
thanks,
--Barry
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-09-27 19:16:41 | Re: [JDBC] Prepared statement performance... |
Previous Message | Barry Lind | 2002-09-27 19:02:02 | Re: [JDBC] Prepared statement performance... |
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-09-27 19:16:41 | Re: [JDBC] Prepared statement performance... |
Previous Message | Barry Lind | 2002-09-27 19:02:02 | Re: [JDBC] Prepared statement performance... |