From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | kumar <kumar(at)cc(dot)usu(dot)edu> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Timestamp problem |
Date: | 2002-06-12 14:57:46 |
Message-ID: | 20020612075641.H90949-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-06-12 16:36:36 | Re: Efficient DELETE Strategies |
Previous Message | Tom Lane | 2002-06-12 14:49:26 | Re: Efficient DELETE Strategies |