It could be used to remove the need for a torque.database.?.adapter property, but this will just complicate unit testing. We could always keep the property and use this as a fallback.
john mcnally On Fri, 2002-05-31 at 10:53, Daniel Rall wrote: > "Bill Schneider" <[EMAIL PROTECTED]> writes: > > >> I just introduced a property to specify the database type or adapter. > >> This used to be specified separately from the driver property and tying > >> them together has caused about as many questions as having the two > >> properties. As you point out there is no way (or we have been unable to > >> find a way) to keep the mapping using datasources. > > > > I may have found a way-- > > conn.getMetaData().getDatabaseProductName() returns String > > - returns "Oracle" in Oracle > > - returns "MySQL" in mysql > > - returns "PostgreSQL" in postgresql > > > > the DatabaseMetaData object returned by conn.getMetaData() seems to return a > > bunch of other useful info too. > > John, have any ideas on where to integrate this in? It seems useful, > but I can't place it off hand. > > -- > 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]>
