R Ravishankar <[EMAIL PROTECTED]> writes:
> Moreover it was found that if we retrieve the resultset as a getString instead of a
>getTimestamp, it returns correctly.
Oh? That suggests that the problem is in JDBC or the underlying JVM.
I'd suggest asking the pgsql-jdbc list about it.
Is it safe to assume that this difference of 30 mins would be consistent even if our
implementation in used across different timezones ?
Moreover it was found that if we retrieve the resultset as a getString instead of a
getTimestamp, it returns correctly.
But the valueOf operator to convert
Actually the Timestamp class does not use Timezone. Timezone in Java 1.3 can be set
only on Calendar class objects. Timestamp inherits some methods from the Date class
but none which concerned with setting timezones :-(
Ravi
Tom Lane <[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] writes:
> > I am
[EMAIL PROTECTED] writes:
> I am using Java 1.3.1 and Postgres 7.1.2 and am writing timestamp without zone info
>to the database using JDBC (my zone is IST or +5:30GMT). I find that there is always
>a time difference of 30 minutes when i read from the database.
> When i query the postgres datab
