Check null should have both @Id and @GenerateValue. In some case, they were combined together.
if you want to update it without select, you might use JPQL to store it. but you have to write your update JPQL. Meanwhile, update JPQL is not recommend in JPA. On 9/21/07, Evgeny Shepelyuk <[EMAIL PROTECTED]> wrote: > > 18.09.07 в 11:30 Gene Woo в своём письме писал(а): > > > why do you want to disable SELECT query? > > > > in my opinion, SELECT is a very important step for merging a detached > > object. If no SELECT, how does JPA know it's a detached object or a new > > object? > > > Acxtually it can check @Id annotated field to check if it's not null. > My question is: if i want this behaviour can i achieve it ? > > > by the way, I thought it's not necessary to persist user after you merge > > it. > Yes correct. My mistake. > -- > Best Regards > Evgeny K. Shepelyuk > -- Best Regards, Gene Woo
