From: Thomas Lockhart <lockhart@alumni.caltech.edu>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Barry Lind <barry@xythos.com>
Cc: pgsql-patches@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Cc: mcannon@internet.com
Subject: Re: [PATCHES] Patch for JDBC timestamp problems
Date: Sat, 13 Jan 2001 16:30:16 +0000
Message-ID: <3A608298.6ACA84BD@alumni.caltech.edu> (raw)
References: <200101130516.AAA14835@candle.pha.pa.us>
> Oh, great, I see this patch fixes Mike Cannon's problem too. I will
> apply it to the main tree now, and it will appear in 7.1. If you have
> any more improvements, please send them over. Thanks.
I'm confused, as usual. How does forcing the client time zone to GMT fix
the problem of mismatching client and server time zones? istm that you
still have a problem if the server is not on GMT.
Does creating a static variable affect the threadsafe capabilities of
the driver? If so, it shouldn't be done, but perhaps this is a feature
of the code already?
- Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: lockhart@alumni.caltech.edu, pgman@candle.pha.pa.us, barry@xythos.com, pgsql-patches@postgresql.org, mcannon@internet.com
Subject: Re: [PATCHES] Patch for JDBC timestamp problems
In-Reply-To: <3A608298.6ACA84BD@alumni.caltech.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox