#392 Should DbUnitAssert.assertEquals(ITable, ITable) throw ComparisonFailure in this situation?

[RafaelVS]

This ticket was create to continue the discussion that started in ticket 386

given
a FlatXmlDataSet created with caseSensitiveTableNames=true with 2 tables named TEST_TABLE_WITH_CASE_SENSITIVE_NAME and test_table_with_case_sensitive_name

when
assertion.assertEquals(dataSet.getTable("TEST_TABLE_WITH_CASE_SENSITIVE_NAME"), dataSet.getTable("test_table_with_case_sensitive_name"));

then
AssertionFailedError should be thrown, as the tables are different because of case sensitive.

but
Assertion doesn't throw any erros, leading to a false positive assertion.

As Jeff pointed out here, there is an old test case that leads us to believe this was intentionally designed to behave like this.

I opened this ticket so that we can discuss if the current behavior of DbUnitAssert.assertEquals(ITable,ITable) actually makes sense and if it does, then if it makes sense to provide a new method in DbUnitAssert that takes isCaseSensitiveTableName into consideration when comparing two ITable's that were obtained from the same IDataSet.