Skip site navigation (1) Skip section navigation (2)

Re: BUG #1611: reading a date-field by "ResultSet.getTimestamp()"

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Ingolf Knopf <iknopf(at)csc-dd(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1611: reading a date-field by "ResultSet.getTimestamp()"
Date: 2005-04-21 21:49:07
Message-ID: 42681FD3.5040108@opencloud.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Ingolf Knopf wrote:
> The following bug has been logged online:
> 
> Bug reference:      1611
> Logged by:          Ingolf Knopf
> Email address:      iknopf(at)csc-dd(dot)de
> PostgreSQL version: 8.0.1
> Operating system:   JDBC
> Description:        reading a date-field by "ResultSet.getTimestamp()"
> method analized dayligth flag
> Details: 
> 
> Retrieving data by "java.sql.ResultSet" I read a data from a column which
> has type DATE. I read content of this column by method
> "ResultSet.getTimestamp( int )".
> I get a "java.sql.Timestamp"-object, where Calendar.HOUR_OF_DAY==1. I
> suppose, this is daylight flag.
> 
> Maybe this behavior of your JDBC driver is compatible with SQL standard, but
> it is completely other than the behavior of "Oracle" or "Ingres".

Can you provide a compilable test case please?

What is the behaviour of Oracle/Ingres with the same test case?

-O

In response to

Responses

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2005-04-22 04:21:49
Subject: Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Previous:From: Sokolov YuraDate: 2005-04-21 19:40:04
Subject: BUG #1616: Inadequate behavior GIST (btree_gist) multicolumn: first not unique

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group