Hello, Rajeev. I repeated the test with enhanced classes and didn't see this behavior. In my test i used OpenJPA 1.0.2.
Best regards Georgi Rajeev Jha wrote: > hello Georgi > Do you see this behavior with enhanced classes also? like when I try > the same test case with enhanced classes , UPDATE is fired for only > the dirty objects. can you please verify this? > > > Thanks > > - rajeev. > > > > On Thu, Mar 27, 2008 at 12:30 PM, Georgi Naplatanov <[EMAIL PROTECTED]> wrote: >> Hello, Bardolf >> >> I created bug report on JIRA - >> https://issues.apache.org/jira/browse/OPENJPA-546 >> >> Let see OpenJPA developer's comments. >> >> Best regards >> Georgi >> >> >> >> bardolf wrote: >> > Hi Georgi, >> > openJPA 1.0.1 does this, but I'm not sure if it is right behaviour. >> > Toplink doesn't call update on unchanged entities, on the other hand it >> > calls update on entity planned to be removed. >> > >> > Bardolf >> > >> > Georgi Naplatanov wrote: >> >> Hello, everybody. >> >> >> >> Is the update on unchanged entities within transaction the right >> >> behavior ? >> >> >> >> It's very important for my applications. >> >> >> >> I wrote the following example and all selected entities were updated : >> >> >> >> factory = >> >> Persistence.createEntityManagerFactory("....",System.getProperties()) ; >> >> em = factory.createEntityManager() ; >> >> em.getTransaction().begin() ; >> >> Query q = em.createQuery("SELECT ......... "); >> >> List l = q.getResultList() ; >> >> System.out.println(l.size()) ; >> >> em.getTransaction().commit() ; >> >> em.close() ; >> >> factory.close() ; >> >> >> >> My environment is : >> >> OpenJPA 1.0.2 >> >> PostgreSQL 8.3.0 >> >> >> >> Best regards >> >> Georgi >> >> >> > >> >>
