Re: Bug in JDBC-Driver?
От | Barry Lind |
---|---|
Тема | Re: Bug in JDBC-Driver? |
Дата | |
Msg-id | 03E7D3E231BB7B4A915A6581D4296CC6CCA759@NSNOVPS00411.nacio.xythos.com обсуждение исходный текст |
Ответ на | Bug in JDBC-Driver? (Antje.Stejskal@ppi.de) |
Ответы |
Re: Bug in JDBC-Driver?
|
Список | pgsql-jdbc |
OK. But IMHO, if you are using timestamps outside of PreparedStatements you are asking for trouble :-). Since you pointed out earlier that most of the timezones match between java and the server, you could first attempt to use the server's timezone, and if that doesn't work you could fall back to this method of using GMT on both client and server. --Barry -----Original Message----- From: Kris Jurka [mailto:books@ejurka.com] Sent: Wednesday, December 22, 2004 3:27 AM To: Barry Lind Cc: Antje.Stejskal@ppi.de; pgsql-jdbc@postgresql.org Subject: Re: [JDBC] Bug in JDBC-Driver? On Mon, 20 Dec 2004, Barry Lind wrote: > I haven't been closely following this thread so I may be completely off > base here. But wouldn't having both java and the server using the same > known timezone have the same effect? So if you were to set the timezone > to GMT in both the client and server, timestamps could then be passed > correctly. > I initially thought this was a great idea, but it breaks down when they don't use a PreparedStatement and generate a query directly, then we can't intervene and adjust things. The advantage of setting the server to the client's timezone is that this will work as expected. Kris Jurka
В списке pgsql-jdbc по дате отправления: