Skip site navigation (1) Skip section navigation (2)

Re: Timestamp weirdness

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: emergency(dot)shower(at)gmail(dot)com, pgsql-jdbc(at)postgresql(dot)org,tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: Re: Timestamp weirdness
Date: 2005-07-26 23:17:47
Message-ID: 42E6C49B.4040404@opencloud.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Kevin Grittner wrote:

> My question (not well stated, I'm sure) was whether there is a way to
> know, on the server, at the point of handling the timestampz from the
> protocol stream, that it is going to be assigned to a TIMESTAMP WITHOUT
> TIME ZONE and use literal assignment rules (i.e., ignore the time zone
> info) instead of the cast rules.  The next question was whether this
> would break existing code.

As I said:

>>>>Oliver Jowett <oliver(at)opencloud(dot)com> 07/26/05 9:20 AM >>>

> If we get the server to infer a type for the parameter rather than
> explicitly specifying it as timestamptz, then we can avoid that cast.
> Then things don't break.

-O

pgsql-jdbc by date

Next:From: Oliver JowettDate: 2005-07-26 23:29:38
Subject: Re: Timestamp Summary
Previous:From: Scott GoldsteinDate: 2005-07-26 22:56:13
Subject: Client Connection vs. JDBC Connections vs. Postgres processes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group