| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | David Johnston <polobo(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: selecting for type cast failures |
| Date: | 2013-03-10 18:51:58 |
| Message-ID: | 513CD64E.3050401@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 03/07/2013 08:56 PM, David Johnston wrote:
> Adrian Klaver-3 wrote
>> My opinion, it would take more time to concoct regexes that cover all
>> the corner cases than to write a script that walks the through the data
>> , finds the problem data and flags them.
>
> ISTM that using regular expressions is necessary regardless of whether you
> put them into a function/script or otherwise use them interactively via
> queries...
Not necessarily. I have done this sort of thing in Python by 'pre'
casting, using Python casting to weed out the problem children.
>
> David J.
>
>
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csanyi Pal | 2013-03-11 06:39:26 | ERROR: relation "employees" does not exist |
| Previous Message | Scott Marlowe | 2013-03-10 13:38:50 | Re: table spaces |