It appears that when you set "globalSequenceId", it doesn't mean "global", it means base it on the column name. This is very misleading, and as it turns out, prone to error. Specifically, in Oracle, column names are case-insensitive, but when we use the "globalSequenceId", their casing matters because it is used to construct an OJB sequence name. The error prone part is that developers don't necessarily case them right in the repository_user.xml.
1) I think there should be a TRULY globalSequenceId option, and this current one should be "columnBasedSequenceId" 2) The columnBased one needs to be (at least in some circumstances) case-insenstive David This message contains information from Equifax Inc. which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e-mail [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
