I appreciate very much your opinions. They'll help me to adjust my approach
to this problem.
As I meant, it wouldn't be "cool" to have hibernate hoarding 50 ids, I
didn't mean the id-gaps and id-loss, that's no problem, but also to lose the
timely clear id alignment in the case of parallel access of the database
with another application... Sure, I'll have timestamps vor that, but... :)
Finally I'll go - certainly - with one sequence per PK.
Thanks
Kind regards, Rawi
--
View this message in context:
http://www.nabble.com/Hibernate%2C-web-application-and-only-one-sequence-for-all-primary-keys-tp25490498p25504364.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
