From: | "Colin 't Hart" <colinthart(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: What happened to the is_<type> family of functions proposal? |
Date: | 2010-09-20 15:31:11 |
Message-ID: | AANLkTi=b799xu1qfrPaLh7vEz8fYW+ihqs+Cze=ks2nO@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 20 September 2010 16:54, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
> On 09/20/2010 10:29 AM, Colin 't Hart wrote:
>>
>> Hi,
>>
>> Back in 2002 these were proposed, what happened to them?
>>
>> http://archives.postgresql.org/pgsql-sql/2002-09/msg00406.php
>
>
> 2002 is a looooooooong time ago.
<snip>
> I think to_date is the wrong gadget to use here. You should probably be using the date input routine and trapping any data exception. e.g.:
>
> test_date := date_in(textout(some_text));
>
> In plpgsql you'd put that inside a begin/exception/end block that traps SQLSTATE '22000' which is the class covering data exceptions.
So it's not possible using pure SQL unless one writes a function?
Are the is_<type> family of functions still desired?
Also, where are the to_<type> conversions done?
Thanks,
Colin
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-09-20 15:37:34 | Re: Do we need a ShmList implementation? |
Previous Message | Markus Wanner | 2010-09-20 15:30:06 | Re: bg worker: general purpose requirements |