1 Reply Latest reply on Sep 28, 2009 6:46 PM by P R

    Postgresql Setval/Nextval Consequences Ignored

    P R Newbie

      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 not.

      The id is annotated using @Id, @SequenceGenerator, and @GeneratedValue.

      Environment is Linux, Java 6, Jboss 5.1, and Postgresql 8.3.

      Anyone have any ideas?