Doing a batch update after a persist

[smokingapipe]

I'm getting a constraint violation exception. Here's what's going on:

1. I create a new entity, and persist it, using the SMPC.

2. I then do a batch update: entityManager.createQuery().executeUpdate(). This query changes all the objects in a class to have a value that is the new entity that I persisted in step 1.

I get a Postgres constraint violation at that point, saying that the entity with the ID that was persisted in step 1 cannot be found in the table.

It seems like it may be a Seam bug, or an EJB3 bug, or some bug in interacting with PG. Any ideas on this? Is there a work-around?

Thanks

[smokingapipe]

I'm wondering if it's related to:

http://jboss.com/index.html?module=bb&op=viewtopic&p=3893197

Any ideas would be welcome.

[smokingapipe]

I found the solution: do an entityManager.flush() after doing the persist(), to flush the new entity to the underlying DB, so that Postgres will be at peace with the universe.