From: | Chris Bowlby <excalibur(at)accesswave(dot)ca> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: issue with an assembled date field |
Date: | 2008-02-29 19:07:11 |
Message-ID: | 1204312031.2839.53.camel@efnisien.dreadnet.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
ho Tom,
Thanks that gave me the brain burp I needed to click into what was
causing the root issue.
On Fri, 2008-02-29 at 13:47 -0500, Tom Lane wrote:
> Chris Bowlby <excalibur(at)accesswave(dot)ca> writes:
> > I am converting an encoded field (lot_id) into a date field, the 5
> > character of every lot_id is always the year and as such I need to
> > extract the year using the following function:
> > substring(ilch.lot_id::text, 5, 1)
>
> Well, I'd say that the failure proves that some of your data does
> *not* have the year in the fifth character.
>
> > ERROR: invalid input syntax for type date: "01/01/0W"
>
> Time for some data sanitizing?
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Gainty | 2008-02-29 19:18:06 | Re: issue with an assembled date field |
Previous Message | Richard Huxton | 2008-02-29 19:04:17 | Re: Insert vs Update syntax |