| From: | Ben <bench(at)silentmedia(dot)com> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: unsupported types in 8.0.1 |
| Date: | 2005-03-26 21:22:24 |
| Message-ID: | 9a086cd3c0aafe69519cc12705984097@silentmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
The way our app is structured, storing unixtime is the most efficient
way to get what we want.
I can't recall why I started using abstime... I started it with some
other projects years ago and was under the impression that it was the
preferred way. Maybe it was then, but isn't anymore? Maybe I'm just
wrong? Anyway, extract() works great, so I'll use that from now on.
Thanks!
On Mar 26, 2005, at 12:41 PM, Michael Fuhr wrote:
> On Sat, Mar 26, 2005 at 12:22:51PM -0800, Ben wrote:
>>
>> Is there a workaround I could use, or should I stick with 7.4 for now?
>
> The documentation discourages using abstime -- is there a reason
> you're using it instead of extract(epoch from now())? That should
> work in the query.
>
> Is there a reason you're using integer instead of timestamp or
> timestamp with time zone?
>
> --
> Michael Fuhr
> http://www.fuhr.org/~mfuhr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-26 21:31:04 | Re: plpgsql no longer exists |
| Previous Message | Tom Lane | 2005-03-26 20:57:56 | Re: unsupported types in 8.0.1 |