Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 332204764D3 for ; Wed, 12 Jun 2002 10:57:48 -0400 (EDT) Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 623DD4764AD for ; Wed, 12 Jun 2002 10:57:42 -0400 (EDT) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id F2BD2D600; Wed, 12 Jun 2002 07:57:46 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id E86F15C01; Wed, 12 Jun 2002 07:57:46 -0700 (PDT) Date: Wed, 12 Jun 2002 07:57:46 -0700 (PDT) From: Stephan Szabo To: kumar Cc: Subject: Re: Timestamp problem In-Reply-To: <3D06EF85@webmail.usu.edu> Message-ID: <20020612075641.H90949-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200206/149 X-Sequence-Number: 8114 On Tue, 11 Jun 2002, kumar wrote: > Hai All, > > I have been using Mysql in which I used unix_timestamp() function > to retrieve the time using the queries. As it gives time in seconds the life > is easy to store it in database and to compare with the other times. But now I > am moving to PostgreSQL in which there is a function current_timestamp to > retrieve time, but now it became hard for me to store it in database in the > string format and to compare it with other times again. What is the specific problem you're having? Do you have an example that illustrates it? In general, I don't know why you'd want to store the timestamp as a string rather than a timestamp.