From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
---|---|
To: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Casting timestamp with time zone to varchar automatically |
Date: | 2004-08-03 16:18:42 |
Message-ID: | 20040803161842.GP88458@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Unfortunatly, that still doesn't really answer my question. I have a
generic function that accepts varchars, and I'd like to be able to feed
it timestamps without explicitly converting. That's why I'd like to know
if there is a specific reason there's no default timestamp -> varchar
cast.
On Tue, Aug 03, 2004 at 03:57:36PM +0900, Michael Glaesemann wrote:
>
> On Aug 3, 2004, at 3:12 PM, Jim C. Nasby wrote:
>
> >Is there any reason why there isn't a predefined cast to go from a
> >timestamp to a varchar? Is there a reason not to add one?
>
> to_char should do what you need. People often need a specific form of
> timestamp if they need it to be a text value (rather than a native
> timestamp data type). to_char provides lots of flexibility
>
>
> Michael Glaesemann
> grzm myrealbox com
>
--
Jim C. Nasby, Database Consultant jim(at)nasby(dot)net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2004-08-03 17:28:27 | Re: NOT IN query takes forever |
Previous Message | Marius Andreiana | 2004-08-03 16:02:42 | Re: NOT IN query takes forever |