Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0DGkop62656; Sat, 13 Jan 2001 11:46:50 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id LAA12663; Sat, 13 Jan 2001 11:46:41 -0500 (EST) From: Bruce Momjian Message-Id: <200101131646.LAA12663@candle.pha.pa.us> Subject: Re: [PATCHES] Patch for JDBC timestamp problems In-Reply-To: <3A608298.6ACA84BD@alumni.caltech.edu> "from Thomas Lockhart at Jan 13, 2001 04:30:16 pm" To: lockhart@fourpalms.org Date: Sat, 13 Jan 2001 11:46:41 -0500 (EST) CC: Barry Lind , pgsql-patches@postgresql.org, pgsql-interfaces@postgresql.org, mcannon@internet.com X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200101/121 X-Sequence-Number: 731 > > 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. No idea. When it fixed someone's problem, I was excited. > > 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? That was a question I had too. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026