[jboss-user] [EJB 3.0 Users] - Postgresql Setval/Nextval Consequences Ignored

Apparently the consequences of using Setval or Nextval in Postgresql --apart from JPA-- is overlooked when JPA selects the next value in spite of JPQ querying the value. I've tried setting the value back to 1 and next-ing the value from Psql then querying it. Psql sees the change yet JPA does

[jboss-user] [EJB 3.0 Users] - Re: Postgresql Setval/Nextval Consequences Ignored

So apparently the default allocationSize is 50 instead of 1. Changing it to 1 has resolved the issue. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4257507#4257507 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4257507