Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id A36079FB418; Tue, 29 May 2007 23:59:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 38847-10; Tue, 29 May 2007 23:59:37 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 4F5979FB77B; Tue, 29 May 2007 23:59:37 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4U2xZko025937; Tue, 29 May 2007 22:59:36 -0400 (EDT) To: Mageshwaran cc: pgsql-general@postgresql.org, pgsql-admin@postgresql.org Subject: Re: Problem with timestamp In-reply-to: <465CE537.9020903@sifycorp.com> References: <465CE537.9020903@sifycorp.com> Comments: In-reply-to Mageshwaran message dated "Wed, 30 May 2007 08:15:11 +0530" Date: Tue, 29 May 2007 22:59:35 -0400 Message-ID: <25936.1180493975@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/312 X-Sequence-Number: 25632 Mageshwaran writes: > We have our application which uses postgres 7.1.3 version in > that we use a time functions like now(),timestamp..... etc mostly > timestamp without timezone.We don't need the timezone in that variable > so we ignore it using timestamp without timezone. The same is not > working with higher versions.We are facing problems in migration. We are > able to store the dates in the database but while retrieving the driver > is not able to retrieve. What "driver" is that, and what goes wrong exactly? regards, tom lane