| From: | wrobell <wrobell(at)posexperts(dot)com(dot)pl> |
|---|---|
| To: | pgsql-patches(at)postgresql(dot)org |
| Subject: | [JDBC] timestamp parsing |
| Date: | 2000-11-20 11:43:01 |
| Message-ID: | 20001120124301.E1889@pred.posexperts.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Current timestamp parsing is quite complex and buggy
in my opinion, i.e. '2000-09-22 13:21:39+02' works (inserted
with now() function) but inserting '2000-09-22 13:21:39.11+02'::timestamp
(important is '.11+02') does not work (as I know). The problem
exists because postgresql _does_not_ show timestamp in unambiguous way.
After applying attached patch, JDBC sets datestyle to SQL and
uses 'MM/dd/yyyy HH:mm:ss.SS zzzz' format to parse a timestamp.
However the question remains. What should be fixed? JDBC or postgresql?
wrobell <wrobell(at)posexperts(dot)com(dot)pl>
| Attachment | Content-Type | Size |
|---|---|---|
| jdbc-timestamp.patch | text/plain | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2000-11-23 11:44:21 | 7.1: to_char(): Y,YY,YYY,YYYY fix |
| Previous Message | Peter Mount | 2000-11-20 08:12:23 | RE: [JDBC] string conversion patch |