Re: You might need to add explicit type casts.

Thank you for the quick response.

I also found that the WHERE statements were not properly quoted, a 101
mistake.

WHERE id = 469 => WHERE id = '469'

The update seems to be working as expected.

kulmacet

> On Sun, 2008-12-28 at 21:30 -0600, kulmacet101(at)kulmacet(dot)com wrote:
>> I have a table running on Linux\Postgresql 8.3.4:
>>
>> CREATE TABLE "public"."active_sessions" (
>> "id" VARCHAR(11) DEFAULT nextval('id_seq'::regclass) NOT NULL,
>> "browser_type" VARCHAR(100),
>> "session_id" VARCHAR(50),
>> "ip_address" INET,
>> "username" VARCHAR(50),
>> "access_time" TIMESTAMP WITHOUT TIME ZONE,
>> "user_rand" VARCHAR(15),
>> "user_activity" TIMESTAMP WITHOUT TIME ZONE,
>> CONSTRAINT "active_sessions_pkey" PRIMARY KEY("id")
>> ) WITHOUT OIDS;
>>
>> I can insert the TIMESTAMP('s) into this table without issue but when I
>> update the new entry the following error is received:
>
> Hi,
>
> You need to:
>
> UPDATE active_sessions SET access_time = '12/28/2008 8:51:33PM'::timestamp
> without time zone WHERE id = 469
>
> or alternatively:
>
> UPDATE active_sessions SET access_time = current_timestamp::timestamp
> without time zone WHERE id = 469
>
> I'm surprised that:
>
> UPDATE active_sessions SET access_time = current_timestamp WHERE id = 469
>
> doesn't also work fine though - it should cast timestamp => timestamp
> without time zone without any trouble.
>
> Cheers,
> Andrew.
>
> ------------------------------------------------------------------------
> andrew (AT) morphoss (DOT) com +64(272)DEBIAN
> You fill a much-needed gap.
> ------------------------------------------------------------------------
>
>
>