It depends on the quality of the JDBC driver and the type of database. >From my experience with using Sun's JDBC-ODBC bridge to read MS Access files (kind of worst case) you can expect any amount of things that are not working. Although it seems much improved with JDK1.4 and Access2000.
So what about using DatabaseMetaData as default and let users override settings (as a fallback) in the (standard)jbosscmp-jdbc.xml files for dumb data sources? Georg -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Jencks Sent: Monday, March 04, 2002 00:25 To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Is DatabaseMetaData safe to use? On 2002.03.03 14:39:50 -0500 Dain Sundstrom wrote: > I have been looking at using DatabaseMetaData extensively in the code > for determining what sql to generate. Is DatabaseMetaData safe to use? > I do remember way back some vendors meta data lied. > It's not supposed to :-) I don't have much personal experience. I think you will have to try and see. There may be some other problems such as DatabaseMetaData makes unwarranted assumptions about whether it has covered all possibilities, so no anwser to their question is correct. (For instance, Firebird does all ddl in transactions, but only at the end of the transaction. So new tables are not visible in the transaction that created them. I ran into trouble once with this not fitting into sun's preconceptions about what is possible) david jencks > -dain > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
