Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] Failed insert results in invalid cache state

Ah! I thought you meant that EclipseLink had its own mechanism for preventing
duplicates. We have been precluded from using any of the implementation
items you have mentioned.

Thanks for your help!

-B


James Sutherland wrote:
> 
> JPA and EclipseLink support three types of sequencing, all three are
> managed by the database, so never generate duplicates.  TABLE uses a
> sequence table in the database, database transaction prevent duplicates,
> IDENTITY uses IDENTITY columns in the database, SEQUENCE uses SEQUENCE
> objects in the database.
> 

-- 
View this message in context: http://old.nabble.com/Failed-insert-results-in-invalid-cache-state-tp25384148p26498518.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.



Back to the top