Re: BUG #5281: Timestamp fields not inserting from 8.3 to 8.4

From: Chris Travers <chris(at)metatrontech(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Jodi Escalante <jescalante(at)assistgroup(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5281: Timestamp fields not inserting from 8.3 to 8.4
Date: 2010-01-15 18:40:31
Message-ID: 5ed37b141001151040t6d4a7da2vee86c03ac9626af6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jan 15, 2010 at 9:38 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> "Jodi Escalante" <jescalante(at)assistgroup(dot)com> wrote:
>
>> INSERT INTO assessment (id, created, taken, current_weight, note,
>> assessment_type, stay_id, contact_id, estimated_discharge_date,
>> cond_chf, cond_pulm_heart, cond_endocrine_other, cond_skin_temp,
>> ) VALUES ( 50,  2008-01-11 15:06:40.257000 -07:00:00,
>> 2008-01-11 00:00:00.000000 -07:00:00,  2000.0,  NULL,  Initial,
>> 3452, 2147,  NULL,  N,  N,  N,  N)
>
> Without quotes you've got the calculation (2008 minus 1 minus 11)
> which equals the integer 1996.  It doesn't know what to make of the
> number which comes next.  Try something like TIMESTAMP WITH TIME
> ZONE '2008-01-11 15:06:40.257000 -0700'.  Similar issues seem to
> exist with most of your other literals.

Just as a note this might have appeared to work in pre-8.3 but may
have done the wrong thing. Definitely quote your literals.

Best Wishes,
Chris Travers

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Treat 2010-01-16 17:47:14 BUG #5283: Missing "base/1/ON" file during initdb
Previous Message Kevin Grittner 2010-01-15 17:38:10 Re: BUG #5281: Timestamp fields not inserting from 8.3 to 8.4