Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 5E780476FA3 for ; Mon, 13 Jan 2003 13:46:24 -0500 (EST) Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 16642476F95 for ; Mon, 13 Jan 2003 13:45:05 -0500 (EST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 1E862D605; Mon, 13 Jan 2003 10:45:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 140AB5C02; Mon, 13 Jan 2003 10:45:05 -0800 (PST) Date: Mon, 13 Jan 2003 10:45:05 -0800 (PST) From: Stephan Szabo To: Josh Berkus Cc: Richard Rowell , Subject: Re: to_date confusion In-Reply-To: <200301131045.50638.josh@agliodbs.com> Message-ID: <20030113104351.F58199-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/181 X-Sequence-Number: 11046 On Mon, 13 Jan 2003, Josh Berkus wrote: > Richard, > > > I'm confused. How do I get the integer 10102 to come in as the date > > 2002-01-01? > > Hmmm ... isn't this an old post, repeating? Yep, my guess is that he sent it, wasn't on the list so it went for approval, he joined and resent, and we're now getting the approved version of it (given that I just received a bunch of messages with dates about a week ago)