Hi all After digging into the documentation, it seems like the Peers class defaulted to using the id_table as the default primary key sequencing method. And the only way to modify its behavior is to modify the MapBuilder class (org.apache.turbine.util.db.map.TurbineMapBuilder) and change its method
from : tMap.setPrimaryKeyMethod(TableMap.IDBROKERTABLE); to : tMap.setPrimaryKeyMethod(TableMap.SEQUENCE); reference link: http://jakarta.apache.org/turbine/turbine-2/howto/peers-howto.html Isn't there a way to set up the primary key sequence method via some configuration file other than having to modify the code and rebuild the entire code base? Am I way off base here ? or does it make sense that The TurbineResource.properties file is already laden with run time settings ? Why not adding a few others? Just curious. Thanks. -----Original Message----- From: Ian Huynh Sent: Thursday, November 29, 2001 2:23 PM To: Turbine Users List Subject: Scheduled Job Problem - Sequence Number question Importance: High Hi I am using Turbine in stand alone mode and I am specifically only using the Schedule Service. I've created the TURBINE_SCHEDULED_JOB according to the documentations instead of using torque. How are the Oracle Sequence number generated? I've also manually created a sequence called TURBINE_SCHEDULED_SEQ ? How do i tell turbine to use the oracle sequence instead of idbroker? Thanks -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
