Denis,
This is more appropriate for the jdbc mail list.
--Barry
Denis Khabas wrote:
Hi everyone:
I am using Postgresql 7.3.4 and found a problem inserting "Timestamp" objects through
JDBC Prepared Statements when the time zone is set to Canada/Newfoundland (3 hours and
30 minutes from MGT). I
On Fri, 19 Mar 2004, Denis Khabas wrote:
> Hi everyone:
> I am using Postgresql 7.3.4 and found a problem inserting "Timestamp"
> objects through JDBC Prepared Statements when the time zone is set to
> Canada/Newfoundland (3 hours and 30 minutes from MGT). I am trying to
> insert "new Timestamp
Hi everyone:
I am using Postgresql 7.3.4 and found a problem
inserting "Timestamp" objects throughJDBC Prepared Statements when the time
zone is set to Canada/Newfoundland (3 hours and30 minutes from MGT). I am
trying to insert "new Timestamp(0L)" into one of the fields.The database
replie
Hi
I found a strange error (at least at first glance I had thought it
seems so):
mail=# select * from accounts_log where login='trading';
id | login | debet | credit | when
--+-+---+---+--
6289 | trading | 117
At 15:13 26/07/01 -0700, Nathan Myers wrote:
>Should pg_dump be lossy?
No it shouldn't, but it already is because it uses decimal text reps of
everything; we lose data when dumping floats as well. In the latter case we
should dump the hex text reps to get the full bit width. Something similar
is
> > > It is not a bug, in general, to generate or accept times like
> > > 09:01:60. Leap seconds are inserted as the 60th second of a minute.
> > > ANSI C defines the range of struct member tm.tm_sec as "seconds
> > > after the minute [0-61]", inclusive, and strftime format %S as "the
> > > second
On Thu, Jul 26, 2001 at 05:38:23PM -0400, Bruce Momjian wrote:
> Nathan Myers wrote:
> > Bruce wrote:
> > >
> > > I can confirm that current CVS sources have the same bug.
> > >
> > > > It's a bug in timestamp output.
> > > >
> > > > # select '2001-07-24 15:55:59.999'::timestamp;
> > > >
> On Wed, Jul 25, 2001 at 06:53:21PM -0400, Bruce Momjian wrote:
> >
> > I can confirm that current CVS sources have the same bug.
> >
> > > It's a bug in timestamp output.
> > >
> > > # select '2001-07-24 15:55:59.999'::timestamp;
> > > ?column?
> > > ---
On Wed, Jul 25, 2001 at 06:53:21PM -0400, Bruce Momjian wrote:
>
> I can confirm that current CVS sources have the same bug.
>
> > It's a bug in timestamp output.
> >
> > # select '2001-07-24 15:55:59.999'::timestamp;
> > ?column?
> > ---
> > 2001-07-
