Well,it looks like it changed the datatype for me. I had INT PRIMARY
KEY DEFAULT NEXTVAL('engineers_id_seq') (I changed the sequence name to
make TLE happy), but now the field is defined as SERIAL NOT NULL.
Pretty strange, but it doesn't seem to be hurting anything, so I'll let
that slide for now. And my app is working without Hibernate in the app
server anywhere, which was my goal.
Thanks for all the help.
-----
Jason Lee, SCJP
Senior Software Engineer
http://www.iec-okc.com
> -----Original Message-----
> From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
> Sent: Friday, March 16, 2007 3:04 PM
> To: users_at_glassfish.dev.java.net
> Subject: Re: RE: Re: TLE vs Hibernate
>
> Jason,
> There is already an ehancement request to track this
> issue :
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=2021 .
> The initial native sequencing support added to the PostgreSQL
> platform was for the SERIAL data type which is effectively
> Identity type sequencing and SEQUENCE type sequencing is not
> supported. You could update PostgreSQL platform to support a
> SEQUENCE (compare it to the Oracle platforms) and provide
> your platform within the persistence.xml properties which
> would provide you with a much more simple workaround.
> You could also switch to a SERIAL datatype for your PKs or
> Table based sequencing.
> --Gordon
> [Message sent by forum member 'gyorke' (gyorke)]
>
> http://forums.java.net/jive/thread.jspa?messageID=208497
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>