Prefixing sequence with schema name in generated sql on oracle

Question

Hi,
We use kodo 3.4 with an oracle database in a J2EE environment.
When we put on the kodo tracing during on of our testcases we see statements being generated like :
select LOOPBAANPERIODESEQUENCE.NEXTVAL from DUAL
When we check the rest of the statements we see :
SELECT * FROM PC52290.EINDELOOPBAAN (EINDELOOPBAAN being a table)
Is there any way to make kodo generate the following statement ?
select PC52290.LOOPBAANPERIODESEQUENCE.NEXTVAL from DUAL
Our kodo.properties we use :
javax.jdo.PersistenceManagerFactoryClass=kodo.jdbc.runtime.JDBCPersistenceManagerFactory
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
kodo.jdbc.DBDictionary=kodo.jdbc.sql.OracleDictionary
kodo.jdbc.ForeignKeyConstraints=true
kodo.LicenseKey=<VALID_LICENSE_HERE>
kodo.Log=DefaultLevel=WARN,SQL=TRACE,Runtime=WARN,Configuration=WARN
kodo.jdbc.Schemas=PC52290
kodo.PersistentClasses= ...
An example of our mapping :
          <class name="LoopbaanPeriode">
               <extension vendor-name="kodo" key="jdbc-sequence-factory" value="native"/>
               <extension vendor-name="kodo" key="jdbc-sequence-name" value="LOOPBAANPERIODESEQUENCE"/>
<extension vendor-name="kodo" key="jdbc-class-ind-value" value="1"/>
<field name="beginDatum"           persistence-modifier="persistent" />
<field name="statuut" persistence-modifier="persistent" />
<field name="loopbaan"                     persistence-modifier="persistent"/>
</class>
regards,
David De Schepper.

Answer 1

Hi David,
When faced with a similar problem, I wrote my own subclass of DBDictionary
(in my case actually a subclass of OracleDictionary), and plugged it into
kodo using the kodo.jdbc.DBDictionary property. My class overrode the
following methods:
public String getFullName(Table, boolean);
public String getFullName(Index);
Then at runtime, these methods stuffed in the correct Schema name for
certain tables and indexes, based on values yoinked from some user
properties.
Not sure if this will help or not in your case.
Cheers!
.droo.
On 4/9/06 2:48 PM, in article [email protected], "David De
Schepper" <David De Schepper> wrote:
yes that works but that is not an option for us.
We have an oracle schema for each developer on our team and don't want to
hardcode it in our mapping file (for obvious reasons)
FYI : kodo 4.0.1 does it correctly (generates PC52290.LOOPBAANPERIODESEQUENCE)
but since i have problems doing the upgrade to kodo 4.0 (with as few code
changes as possible) i'm going to have to advice my company not to do the
upgrade.
(In case you are intersted or have some time :
http://forums.bea.com/bea/thread.jspa?forumID=500000029&threadID=600017073&mes
sageID=600041994#600041994)