DBunit; confusion over case sensitivity on table/column names

Question

I\'m getting this error when I start up my application

Caused by: org.dbunit.dataset.NoSuchColumnException: CLIENT.ID -  (Non-uppercase input column: ID) in          


        

Answer 1

Aren't you trying to put to database Client with ID already set? ID column is read-only, only database can "write" to it.

Answer 2

I have fixed the error by adding the mentioned column to my entity.

Answer 3

I ran into the same error, fortunately we had some other test written earlier and found that in most of the tutorials the format the way the xml is written is for the FlatXMLDataSet if you are using XML data set then the correct version is as follow checkout the link at the bottom for more information.

it should be in following format.

<?xml version="1.0" encoding="UTF-8"?>
<dataset>
    <table>
        <column>id</column>
        <column>name</column>
        <column>department</column>
        <column>startDate</column>
        <column>endDate</column>
        <row>
            <value>999</value>
            <value>TEMP</value>
            <value>TEMP DEPT</value>
            <value>2113-10-13</value>
            <value>2123-10-13</value>
        </row>
    </table>
</dataset>

For more information go to this link.

http://dbunit.sourceforge.net/components.html#FlatXmlDataSet

One more time I faced this error in another project, we have a hierarchy of model class, some how hibernate used to create a table Role with 7 columns but while running it with DBUnit it was unable to create the columns(Only 5 were created) hence it was throwing this error, Solution : Manually created this table and 3 more relationship tables which were not created by hibernate.

Answer 4

this error goes away with mysql and hsql if you make format = flat

Answer 5

I've also had this problem after adding a column to one of my entities (using an in-memory HSQL database).

I managed to solve this problem by simply deleting the temporary files that had previously been generated: mem:testdb.log, mem:testdb.properties and mem:testdb.script

Why did this error occur? => A database schema is stored in the mem:testdb.script file and is not re-generated when the entity is modified.