roy
Sent: Friday, December 15, 2006 5:18 PM
To: Tom Lane
Cc: Richard Huxton; Randy Shelley; pgsql-general@postgresql.org
Subject: Re: [GENERAL] TIMESTAMP WITHOUT TIME ZONE
> Richard Troy <[EMAIL PROTECTED]> writes:
> > See my post from a few minutes ago, but simply put, time/date is at
l
Richard Troy <[EMAIL PROTECTED]> writes:
> That said, nobody has yet assured me that when I give a timestamp I get it
> back unmolested.
Well, as far as the backend is concerned you do get it back unmolested
(up to the limits of float roundoff error, if you use float timestamps):
* unconditional
Richard Troy wrote:
> I'd appreciate a clean yes/no; From a Java application, throught PG in
> both directions, the same timestamp comes back that was handed to the JDBC
> driver so long as it's stored in a "timestamp without time zone"
> attribute, nomatter neither where on earth the insert/upda
> Richard Troy <[EMAIL PROTECTED]> writes:
> > See my post from a few minutes ago, but simply put, time/date is at least
> > as challenging as money or multibyte character. And, simply put, the
> > Postgres implementation of timezone is INSUFFICIENT.
>
> Really? We do all the things you have list
Richard Troy <[EMAIL PROTECTED]> writes:
> See my post from a few minutes ago, but simply put, time/date is at least
> as challenging as money or multibyte character. And, simply put, the
> Postgres implementation of timezone is INSUFFICIENT.
Really? We do all the things you have listed, and more
On Fri, Dec 15, 2006 at 12:10:24PM -0800, Richard Troy wrote:
> > I think your fundamental error is in using timestamp without time zone
> > in the database. Try with-time-zone if you want consistent results
> > across clients in different zones.
>
> I sure hope there's no issue with using timest
On Wed, 13 Dec 2006, Richard Huxton wrote:
> Randy Shelley wrote:
> > I get different result if I query it from my workstation(US/Easter
> > timezone) and from the server (GMT timezone).
>
> > A data type of timestamp without time zone should not do any
> > conversions. The java.sql.Timestamp doe
Richard Troy <[EMAIL PROTECTED]> writes:
> I'm not fully caught up with my Readings In Postgres, but this post caught
> my eye and raised a concern...
AFAIK, all the reasons you enumerate are good reasons to delegate the
problem to a timestamp WITH time zone column.
> First, you need at least min
Hi Tom, Randy, et al,
I'm not fully caught up with my Readings In Postgres, but this post caught
my eye and raised a concern...
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Randy Shelley" <[EMAIL PROTECTED]> writes:
> > The java.sql.Timestamp does not store any timezone info, just nano seconds
> > fro
Randy Shelley wrote:
I get different result if I query it from my workstation(US/Easter
timezone) and from the server (GMT timezone).
A data type of timestamp without time zone should not do any
conversions. The java.sql.Timestamp does not store any timezone info,
just nano seconds from a dat
"Randy Shelley" <[EMAIL PROTECTED]> writes:
> The java.sql.Timestamp does not store any timezone info, just nano seconds
> from a date.
One would hope that it's implicitly referenced to GMT, though, not some
free-floating value that means who-knows-what.
I think your fundamental error is in using
Antony Paul wrote:
Hi all
What is the last value in a column of data type timestamp without time
zone. A sample data is 2004-06-22 18:07:00.486027. What does 486027 mean
Milliseconds or seconds since midnight or something else ?
It's fractional seconds, but your clock is unlikely to be that a
12 matches
Mail list logo
