Description geo.temp 2011-07-28 04:33:13 EDT

Build Identifier: EclipseLink, version: Eclipse Persistence Services - 2.1.2.v20101 206-r8635

The order of SQL is NOT the same as the sequence of calling EntityManager.persist() if @GeneratedValue(strategy=GenerationType.IDENTITY) has been defined for the Entity.

The order of SQL is verified by observing the console log after setting eclipselink.logging.level=FINE.

Reproducible: Always

Steps to Reproduce:
1. Create an Entity (TestAudit in this case) whose @Id has @GeneratedValue(strategy=GenerationType.IDENTITY)

2. Get an EntityManager and persist a list of entities in order:

        UserTransaction ut = (UserTransaction) context.lookup("java:comp/UserTransaction");

        ut.begin();
        EntityManager em = ...

	testAudit = new TestAudit();
	testAudit.setValue("1 "+d);
	em.persist(testAudit);

	testAudit = new TestAudit();
	testAudit.setValue("2 "+d);
	em.persist(testAudit);

	testAudit = new TestAudit();
	testAudit.setValue("3 "+d);
	em.persist(testAudit);

	testAudit = new TestAudit();
	testAudit.setValue("4 "+d);
	em.persist(testAudit);

	testAudit = new TestAudit();
	testAudit.setValue("5 "+d);
	em.persist(testAudit);
        
        ut.commit();

3. After committing the transaction, it is found that the order of the final insert SQLs into the database is NOT the same as the order of calling em.persist(testAudit). (Refer to attached eclipseLink.log)