Frontbase metadata with DBUnit not working
Frontbase metadata with DBUnit not working
- Subject: Frontbase metadata with DBUnit not working
- From: Greg Brown <email@hidden>
- Date: Fri, 08 Feb 2013 06:34:01 -0500
| Hello,
Does anybody use Frontbase with DBUnit? I have recently upgraded a project and the newer versions of Frontbase are causing some problems with dbunit.
I have changed some testing code and everything works (ah…so far..) except writing out the database schema with dbunit, something like:
FlatDtdDataSet.write(dout, new FileOutputStream(dtdname));
which causes an exception because it can't find or validate the metadata:
org.dbunit.dataset.NoSuchTableException: Did not find table 'INFORMATION_SCHEMA_CATALOG_NAME' in schema 'null' at org.dbunit.database.DatabaseTableMetaData.<init>(DatabaseTableMetaData.java:146) at org.dbunit.database.DatabaseDataSet.getTableMetaData(DatabaseDataSet.java:293) at org.dbunit.dataset.xml.FlatDtdWriter.write(FlatDtdWriter.java:94) at org.dbunit.dataset.xml.FlatDtdDataSet.write(FlatDtdDataSet.java:111) at org.dbunit.dataset.xml.FlatDtdDataSet.write(FlatDtdDataSet.java:99)
I had similar problems with table names, it seems a case issue with metadata and setting a dbunit property:
fixed that. It seems that the case-insensitive default just up-cases all names, then it looks for the up-cased table name. It does not seem case insensitive to me, as the case-insensitive default can not find tables with mixed case, like "WoodenTable"
Frontbase seems to change a little with each version; I noted awhile back that WOlips could not reverse engineer the latest version of a Frontbase db, previous versions could be reverse engineered. Again, probably a metadata issue.
Greg Brown
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden