Yep, I think that this is a bug of some sort. We're using the sequence:
28516313> executing prepstmnt 1772552 SELECT NEXTVAL('CategoryIdSeq')
but we're just selecting the next value, not the increment size. It's
weird that we are then using the increment size in the returned
values, though.
Does anyone know the syntax in Postgres to select a batch of numbers from a seq?
-Patrick
On 9/20/07, ben short <[EMAIL PROTECTED]> wrote:
> My work around was to set the allocationSize property to 1, but that
> kind of defeats the point of caching the id's.
>
> Regards
>
> Ben
>
> On 9/20/07, Takeichi Kanzaki Cabrera <[EMAIL PROTECTED]> wrote:
> > I have the same problem using postgresql + openjpa-1.0 and at this
> > time I have no solution for it.
> >
> > --
> > Regards,
> > Takeichi Kanzaki Cabrera
> > Linux Registered User #308138
> >
> > If you want to be original,
> > be your self.
> >
>
--
Patrick Linskey
202 669 5907
