Please send a patch to get your driver included in DBFactory. There is not much reason to recode to the old style. Soon torque will use any connection pool and the adapter will be specified in the properties file. Similar to the old way, but there will be no tie between the adapter and the driver (if a driver is even used.)
john mcnally Humberto Hernandez Torres wrote: > > I was trying to make Scarab run with MS SQL but my driver JDBC wasn�t being > recognized. After looking around for a while and downloading the CVS sources > for torque-3.0. I found that in org.apache.torque.adapter.DBFactory there is > a map with the databases and the available drivers. This mapping didn�t seem > to be there in the previous versions and I don�t think it should be > hardcoded since it makes you loose the flexibility to use your favorite JDBC > driver. > > �What is the purpose of the new version? �Shouldn't we go back to the > previous configurable adapters? > > This used to work in TurbineResources.properties: > services.DatabaseServices.database.adaptor=DBMSSQL > services.DatabaseServices.database.DBMSQL=com.jnetdirect.jsql.JSQLDriver > > -- > Humberto > > -- > 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]>
