Hi,
fixed in CVS (OJB 1.0.x branch OJB_1_0_RELEASE)
Armin
Armin Waibel wrote:
Hi Pulat,
Pulat Yunusov wrote:
Currently, all PersistenceBrokers that use SequenceManagerHighLowImpl share one Map for keeping sequences. That map keys sequences essentially by table name in many common cases.
I understand if two databases have tables with the same name, accessing them within a single OJB instance will lead to corruption of the sequence manager's internal map as one entry can potentially be replaced with another with the same key (same table name).
yep, if two databases have tables with the same name and PK columns (more exactly, columns declared as autoincrement in repository) have the same name too.
Is this a valid and a known problem and are you aware of any workarounds?
you are right this could be an issue.
I will fix this by using a static map with the jcdAlias name (defined in repository, have to be unique for each jdbc-connection-descriptor) as key and then per jcdAlias a map keeping the sequences by sequence name.
regards, Armin
Thank you,
Pulat
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
