Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 623BD9FB227 for ; Thu, 5 Oct 2006 17:46:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 87509-05 for ; Thu, 5 Oct 2006 20:45:40 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by postgresql.org (Postfix) with ESMTP id C27F49F95E1 for ; Thu, 5 Oct 2006 17:45:40 -0300 (ADT) Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GVa67-00027J-IC for pgsql-sql@postgresql.org; Thu, 05 Oct 2006 13:45:39 -0700 Message-ID: <6668169.post@talk.nabble.com> Date: Thu, 5 Oct 2006 13:45:39 -0700 (PDT) From: chrisj To: pgsql-sql@postgresql.org Subject: Re: Assigning a timestamp without timezone to a timestamp In-Reply-To: <20061005203121.GI8826@phlogiston.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: chrisj.wood@sympatico.ca References: <6613652.post@talk.nabble.com> <20061003135623.GB3191@phlogiston.dyndns.org> <6621346.post@talk.nabble.com> <20061003145134.GA3399@phlogiston.dyndns.org> <8C5B026B51B6854CBE88121DBF097A864DE848@ehost010-33.exch010.intermedia.net> <20061005183128.GD8826@phlogiston.dyndns.org> <6667446.post@talk.nabble.com> <20061005203121.GI8826@phlogiston.dyndns.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200610/72 X-Sequence-Number: 26461 Thanks for the heads up, I definately need EST5EDT you saved me twice!! Andrew Sullivan wrote: > > On Thu, Oct 05, 2006 at 01:06:00PM -0700, chrisj wrote: >> If only all time zones were fixed offset timezones life would be so much >> simpler. > > Indeed. > >> Unfortunately the main area of deployment of my app will beToronto which >> is >> on EDT which is not a fixed offsets timezone. I hope/assume your >> solution >> works with "EDT" instead of "-3", I will test it soon. > > Should do, although you'll need more than EDT. EDT is also fixed: > it's UTC-4. EST5EDT isn't, though, so you could use that (you'd need > to improve your schema, though, because you had char(3) there, and > not all time zones are 3 characters long). But to answer your > question, yes, it works. I just tried it. > > A > > > -- > Andrew Sullivan | ajs@crankycanuck.ca > Information security isn't a technological problem. It's an economics > problem. > --Bruce Schneier > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > > -- View this message in context: http://www.nabble.com/Assigning-a-timestamp-without-timezone-to-a-timestamp-with-timezone-tf2373845.html#a6668169 Sent from the PostgreSQL - sql mailing list archive at Nabble.com.