Applies to:
DBUnit
Description:
This error occurs when no schema is specified and that DbUnit detect that it is getting columns information from multiple tables having the same name and located in different schemas
Cause:
a. No schema is specified.
B. Your database contains two tables whose names only differ by case, e.g. “userlist” and “UserList”. DBUnit handles table names case-insensitively and gets confused. This can happen on database systems that are case-sensitive for identifiers, e.g. MySQL and (possibly) Microsoft SQL Server.
admin JAVA-DBUnit
Applies to:
DBUnit
Description:
By default, DbUnit only supports standard JDBC data types. This error will occur while using vendor-specific data types
Cause:
You are getting this warning message if you are using vendor-specific data types.
admin JAVA-DBUnit
Applies to:
DBUnit
Description:
Occurs when using InsertIdentityOperation
Cause:
SelectMethod=cursor parameter is missing in the JDBC connection string.
admin JAVA-DBUnit
Applies to:
DBUnit
Description:
Occurs when using DBUnit with the DB2 driver
Cause:
JDBC 2.0 is not installed.
admin JAVA-DBUnit
Applies to:
DBUnit, SLF4J
Description:
Occurs when using DBUnit
Cause:
Since version 2.2.1, DbUnit uses SLF4J for logging purposes. So probably SLF4J is missing.
admin JAVA-DBUnit
Applies to:
DBUnit, Jakarta Commons Logging
Description:
Occurs when using DBUnit
Cause:
You have more then one slf4j implementation library in your classpath.
admin JAVA-DBUnit
Applies to:
DBUnit, MySQL
Description:
Occurs when using DBUnit
Cause:
This exception can occur especially with MySQL RDBMS if you forget to set the special MySqlMetadataHandler on the DatabaseConfig.
admin JAVA-DBUnit