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 f0DHErp64251; Sat, 13 Jan 2001 12:14:53 -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 MAA16317; Sat, 13 Jan 2001 12:14:47 -0500 (EST) From: Bruce Momjian Message-Id: <200101131714.MAA16317@candle.pha.pa.us> Subject: Re: [PATCHES] Patch for JDBC timestamp problems In-Reply-To: <3A608C8A.B0DDEC51@alumni.caltech.edu> "from Thomas Lockhart at Jan 13, 2001 05:12:42 pm" To: lockhart@fourpalms.org Date: Sat, 13 Jan 2001 12:14:47 -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/123 X-Sequence-Number: 733 > > > 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. > > Well, afaict it might have broken most other people, so is not a big > win. That bad, huh? The reason I posted the patch in the email is because I don't understand Java and wanted to make sure other people reviewed it, especially because we are in beta. It dealt with date/time stuff, which made it double-complex. I am ready to yank it if someone gives the word. -- 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