| From: | "Rainer Mager" <rmager(at)vgkk(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | RE: timestamps cannot be created without time zones |
| Date: | 2001-08-26 23:16:04 |
| Message-ID: | NEBBJBCAFMMNIHGDLFKGCELBENAA.rmager@vgkk.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Ok, I now understand more about how Postgres handles these older dates but
we're still seeing a problem that I'm not sure how to handle. Simply put, we
write a TIMESTAMP via JDBC and then read it back. What we write and what we
read are different. The only way I can think of fixing the problem is having
a check, in our code, to see if the dates are earlier than Postgres' magic
cutoff day, and, if so, do timezone fixes. This is bad. Is there a better
way. Is there, perhaps, a bug in the JDBC driver?
Thanks,
--Rainer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matteo Nastasi | 2001-08-27 16:58:43 | Drop function from a batch file error |
| Previous Message | Bruce Momjian | 2001-08-26 17:09:29 | Re: [JDBC] Re: Bug #428: Another security issue with the JDBC driver. |