Mailing-List: contact empire-db-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: empire-db-dev@incubator.apache.org
Date: Mon, 21 Feb 2011 19:44:38 +0000 (UTC)
From: "Eike Kettner (JIRA)" <empire-db-dev@incubator.apache.org>
To: empire-db-commits@incubator.apache.org
Message-ID: 
 <2008963860.6481.1298317478761.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (EMPIREDB-81) endless loop in
 DBSeqTable#getNextValue()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/EMPIREDB-81?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D129=
97542#comment-12997542 ]=20

Eike Kettner commented on EMPIREDB-81:
--------------------------------------

Hi,

I have used Postgre 8.4 with jdbc driver 8.4-702.jdbc which now works very =
well.=20

thanks for fixing!

regards, Eike

> endless loop in DBSeqTable#getNextValue()
> -----------------------------------------
>
>                 Key: EMPIREDB-81
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-81
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: empire-db-2.0.6-incubating
>         Environment: linux (debian) + postgre sql 8.3 and 8.4
>            Reporter: Eike Kettner
>            Assignee: Rainer D=C3=B6bele
>             Fix For: empire-db-2.1.0-incubating
>
>
> I use postgre sql and getting the next sequence value, the getNextValue()=
 goes into an endless loop. It fails when updating the sequence value and t=
herefore tries again and again and again...
> It cannot update the sequence because postgre sql stores milli and nanose=
conds within the timestamp. The WHERE clause from the update omit the milli=
 and nanoseconds. So it tries to update ... WHERE timestamp=3D'2010-06-10 1=
4:22:24'  but in DB it is '2010-06-10 14:22:24.21231'.  The update fails an=
d the loop does never stop. It would be great to be informed somehow if the=
 loop goes beyound some big value.  I did not dig into this deeper, but her=
e is some SQL excerpt:
> CREATE TABLE wb_sequence_generator
> (
>   seqname character varying(40) NOT NULL,
>   seqtime timestamp without time zone NOT NULL,
>   seqvalue bigint NOT NULL,
>   CONSTRAINT wb_sequence_generator_pkey PRIMARY KEY (seqname)
> )
> WITH (
>   OIDS=3DFALSE
> );
> insert into wb_sequence_generator (seqname, seqtime, seqvalue) values ('t=
hetest', NOW(), 2);
> select * from wb_sequence_generator;
> Output:
> "thetest"  ;  "2010-06-29 09:39:56.360305" ;  2

--=20
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira