Re: Bad Date field - Mailing list pgsql-admin

From DHSC Webmaster
Subject Re: Bad Date field
Date
Msg-id 3C0669F3.54DC7842@dhs-club.com
Whole thread Raw
In response to Bad Date field  (Peralta Miguel-MPERALT1 <Miguel.Peralta@motorola.com>)
List pgsql-admin
You could use a perl script to read your data and do a pattern match for
consistency with your date output. Or you could import the data into a
temp table which has a text field instead of date. You could query
against your temp table to find offending data. Then use SQL to insert
the data into your real table.

Peralta Miguel-MPERALT1 wrote:
>
> Hello everyone:
>
> Would anyone know how to find a bad date field in an external file?  I have
> an external file that I am using to populate a table using the following
> command:
> COPY release_data FROM '/home/mperalta/release_data' USING DELIMITERS '|'
>
> When I issue this command, the response afte a while is the following:
>
> ERROR; Bad date external representation '9'
>
> The external file is rather large and I've tried finding this bad date
> manually with no success.  The table I'm copying into has a datestamp of
> type DATE.
>
> Any suggestions would be greatly appreciated.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

--
Bill MacArthur
Webmaster
DHS Club

pgsql-admin by date:

Previous
From: Peralta Miguel-MPERALT1
Date:
Subject: Bad Date field
Next
From: bangh
Date:
Subject: Re: Bad Date field