Jason van Zyl wrote:
> > Dave Polito wrote:
> >
> > Here you go. I have tested SapDB against our application, and it
> > works fine. There are a couple of tricks with the jdbc driver to get
> > it to work. I'm waiting for replies on my proposal for changing the
> > way the database properties are used. Then I could provide a doc on
> > using SapDB.
> Are all your changes backward compatible with the TR.properties? This
> close to a release we couldn't include anything that required
> people to change their properties files. I haven't looked to
> closely to your proposal yet, sorry.
Yes it will be 100% backward compatible. If would require moving code
around in Turbine only.
Example of the TR.properties file only;
Valid Option 1 (as it is now):
database..url=jdbc:sapdb://HOSTNAME/DATABASE?sqlmode=oracle&autocommit=on
database..driver = com.sap.dbtech.jdbc.DriverSapDB
database..username = USERNAME
database..password = PASSWORD
Valid Option 2:
database..url=jdbc:sapdb://HOSTNAME/DATABASE?sqlmode=oracle&autocommit=on
database..driver = com.sap.dbtech.jdbc.DriverSapDB
database..username = USERNAME
database..password = PASSWORD
database..sqlmode = oracle
database..autocommit = on
Valid Option 3:
database..url=jdbc:sapdb://HOSTNAME/DATABASE
database..driver = com.sap.dbtech.jdbc.DriverSapDB
database..username = USERNAME
database..password = PASSWORD
database..sqlmode = oracle
database..autocommit = on
Note that any additional property after database..* would not require
additional coding. I would like be able to take advantage of reading these
properties in the DB adapter code.
Dave Polito
