dbunit-developer

[dbunit-developer] [ dbunit-Feature Requests-3147832 ] Update DBunit to POI 3.7

[SourceForge.net <no...@so...>]

Feature Requests item #3147832, was opened at 2010-12-29 22:09
Message generated for change (Comment added) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449494&aid=3147832&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Next Release
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Ralf Mühle (ralfmuehle)
Assigned to: Nobody/Anonymous (nobody)
Summary: Update DBunit to POI 3.7

Initial Comment:
Hi

I've created a svn-patch to update the last release of DBUnit to POI 3.7. Please check it and if you think that is good you could use it

Best regards,
Ralf

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2011-11-02 10:36

Message:
Our production code needs POI 3.7.  With Maven it isn't possible to use 3.2
in the DBUnit tests and 3.7 in the production code, because the test
classpath supplements the main classpath.
I am sure there are other users in this situation.

----------------------------------------------------------------------

Comment By: Ralf Mühle (ralfmuehle)
Date: 2010-12-30 10:56

Message:
Yes there is a reasen: We need Support of the new Excel format so that we
can load huge excel files. More than 66000 lines and we get the (testing)
data in the new excel format

The patch I've created is an example how you can support both format,s the
old and the new one.

----------------------------------------------------------------------

Comment By: Roberto Lo Giacco (rlogiacco)
Date: 2010-12-30 10:10

Message:
Is there any specific reason for the update? Any missing feature, solved
bug or anything like that? Usually upgrades for the sake to stay on most
recent version are not convenient: they tend to break instead to solve...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449494&aid=3147832&group_id=47439

Re: [dbunit-developer] Where to find JDBC JDBC 2.0 Optional Package Binary

[Jeff J. <jj...@ap...>]

The confusion cause is the new Oracle landing page, instead of the original
Sun page.  Hmmm, I glanced through and did not see anything obvious.  I
stopped at the click-through to JDBC driver page due to time, but might be
there.

Since JDBC 2 is old, perhaps these instructions should change.  It's been
awhile since I have done a new setup!

If you can't find it, try setting up without it and see if/where it fails.
Maybe something in newer JDBC deps replaces it?

Additionally, search Maven Central for the jar, if that is all that is
needed, as it might be there.

I will look further when I can make time to try this in detail.. hopefully
you can proceed in the meantime!
On Oct 31, 2011 1:37 PM, "Ryan Golhar" <ngs...@gm...> wrote:

[dbunit-developer] Where to find JDBC JDBC 2.0 Optional Package Binary

[Ryan G. <ngs...@gm...>]

Hi - I'm trying to contribute a patch to incorporate MySQL XML dump
support.  In the instructions for contributing patches (
http://www.dbunit.org/building.html), the second step says "Download JDBC JDBC
2.0 Optional Package Binary<http://java.sun.com/products/jdbc/download.html>"
however the page is a generic page.  Where do I get this optional package
from?  I can't seem to locate it.

[dbunit-developer] Slow metadata queries

[David K. <dav...@go...>]

Hello dbunit developers,
a few weeks ago I have posted a question on the users-list about a slow
tableExists() (on MS SqlServer 2008 R2):

http://sourceforge.net/mailarchive/forum.php?thread_name=CABGTCTqrqSU9L8Jv8ERp8ZdzVAASs4zpSbCBGvbHFa2Ue2xjAA%40mail.gmail.com&forum_name=dbunit-user

To summarize, the tableExists query during table exports and imports takes
quite long, namely about a third of the total time needed (by my tests at
least). I have tried and commented out the respective lines in
DatabaseTableMetaData leading to exactly that performance improvement, of
course, now without checking whether the table exists.
Of course, now these two unit tests fail

org.dbunit.database.DatabaseTableMetaDataIT.testCreation_UnknownTable
org.dbunit.database.DatabaseTableMetaDataIT.testCaseSensitive

I am wondering whether the call to tableExists is really so important, given
its costs. At least in my understanding sensible exceptions will be thrown
at the latest when the tables are accessed. Or am I just missing some
configuration option that turns out the call to tableExists()?
Any help and / or comments are welcome.

  Cheers,
     David

[dbunit-developer] [ dbunit-Bugs-3422834 ] Unquoted column names in SQL statements

[SourceForge.net <no...@so...>]

Bugs item #3422834, was opened at 2011-10-13 04:45
Message generated for change (Comment added) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3422834&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: v2.4.*
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: matthias g (gommma)
Summary: Unquoted column names in SQL statements

Initial Comment:
When the column names are not quoted for SQL statements, certain column names which use special characters cause inserts to fail.
For example, columns with names containing "#" cannot be inserted because org.dbunit.operation.InsertOperation#getOperationData creates an SQL statement which does not quote the columns; end result is you end up with something like the following:
insert into MYTABLE(COL#,DESC) values(1,'HI');
which fails on some databases (specifically, HSQLDB for this example) because '#' is considered an illegal character.
But if the statement were produced like the following:
insert into MYTABLE("COL#","DESC") values(1,'HI');
the insert succeeds.

Simply quoting all of the time may not be a solution, since this makes a case-insensitive column name into a case-sensitive one, but quoting the column name retrieved from the db meta-data should provide a consistent result.

----------------------------------------------------------------------

>Comment By: https://www.google.com/accounts ()
Date: 2011-10-13 05:45

Message:
Sorry! Realized that you've already thought of this;
I set the property "http://www.dbunit.org/properties/escapePattern" to
value of "\"?\"" and that does the trick.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3422834&group_id=47439

[dbunit-developer] [ dbunit-Bugs-3422834 ] Unquoted column names in SQL statements

[SourceForge.net <no...@so...>]

Bugs item #3422834, was opened at 2011-10-13 04:45
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3422834&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: v2.4.*
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: matthias g (gommma)
Summary: Unquoted column names in SQL statements

Initial Comment:
When the column names are not quoted for SQL statements, certain column names which use special characters cause inserts to fail.
For example, columns with names containing "#" cannot be inserted because org.dbunit.operation.InsertOperation#getOperationData creates an SQL statement which does not quote the columns; end result is you end up with something like the following:
insert into MYTABLE(COL#,DESC) values(1,'HI');
which fails on some databases (specifically, HSQLDB for this example) because '#' is considered an illegal character.
But if the statement were produced like the following:
insert into MYTABLE("COL#","DESC") values(1,'HI');
the insert succeeds.

Simply quoting all of the time may not be a solution, since this makes a case-insensitive column name into a case-sensitive one, but quoting the column name retrieved from the db meta-data should provide a consistent result.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3422834&group_id=47439

[dbunit-developer] [ dbunit-Bugs-3416409 ] Date type conversion does not work with Java 7

[SourceForge.net <no...@so...>]

Bugs item #3416409, was opened at 2011-09-30 21:11
Message generated for change (Tracker Item Submitted) made by ljnelson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3416409&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Laird Nelson (ljnelson)
Assigned to: matthias g (gommma)
Summary: Date type conversion does not work with Java 7

Initial Comment:
org.dbunit.dataset.datatype.TypeCastException: Error casting value for table 'foo.bar' and column 'CREATED_ON'
	at org.dbunit.operation.AbstractBatchOperation.execute(AbstractBatchOperation.java:190)
	at org.dbunit.operation.CompositeOperation.execute(CompositeOperation.java:79)
	at org.dbunit.AbstractDatabaseTester.executeOperation(AbstractDatabaseTester.java:190)
	at org.dbunit.AbstractDatabaseTester.onSetup(AbstractDatabaseTester.java:103)

This was caused by:

Caused by: org.dbunit.dataset.datatype.TypeCastException: Unable to typecast value <2010-20-10 10:30:45> of type <java.lang.String> to DATE
	at org.dbunit.dataset.datatype.DateDataType.typeCast(DateDataType.java:106)
	at org.dbunit.dataset.datatype.DateDataType.setSqlValue(DateDataType.java:141)
	at org.dbunit.database.statement.SimplePreparedStatement.addValue(SimplePreparedStatement.java:73)
	at org.dbunit.database.statement.AutomaticPreparedBatchStatement.addValue(AutomaticPreparedBatchStatement.java:63)
	at org.dbunit.operation.AbstractBatchOperation.execute(AbstractBatchOperation.java:186)
	... 42 more
Caused by: java.lang.IllegalArgumentException
	at java.sql.Date.valueOf(Date.java:140)
	at org.dbunit.dataset.datatype.DateDataType.typeCast(DateDataType.java:102)

Java 7 on Windows 7.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3416409&group_id=47439

Re: [dbunit-developer] [ dbunit-Patches-3048571 ] Support delta for Double data type

[Jeff J. <jj...@ap...>]

Sorry again - I moved it back to feature requests tracker.  Something's up
with the privs on patches one... didn't bother to fix that.

Subversive.  I don't know where there is another Eclipse patch option except
Team -> Apply Patch.


On Thu, Sep 8, 2011 at 4:04 PM, Robin Rosenberg
<rob...@gm...>wrote:

> Jeff Jensen skrev 2011-09-08 20.06:
> > Sorry - I moved the entry to the patch tracker.  You'll find it there...
> >
> Do you have a link? I looked in the Bugs and Feature request trackers
> and these are the only trackers
> I see under the dbunit project.
>
> > Eclipse's svn patch tool does not recognize git (and please show me
> > how to make it do so if you know how!).
> Subclipe or subversion?
>
> Eclipse standard patch tool (non-team provider specifik)  understands
> unidiff patches,  including the ones
> produced by git (as long as extensions aren't used, and I'm pretty sure
> I didn't use any because none were needed).
> Of course it ignores the comment/author stuff so I guess it's less
> convenient.
>
> -- robin
> > On Thu, Sep 8, 2011 at 9:14 AM, Robin Rosenberg
> > <rob...@gm... <mailto:rob...@gm...>> wrote:
> >
> >     SourceForge.net skrev 2011-08-27 02.34:
> >     > Patches item #3048571, was opened at 2010-08-19 05:14
> >     > Message generated for change (Comment added) made by jeffjensen
> >     > You can respond by visiting:
> >     >
> >
> https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
> >     <
> https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
> >
> >     >
> >     > Please note that this message will contain a full copy of the
> >     comment thread,
> >     > including the initial issue submission, for this request,
> >     > not just the latest update.
> >     > Category: None
> >     > Group: None
> >     > Status: Open
> >     > Resolution: None
> >     > Priority: 5
> >     > Private: No
> >     > Submitted By: Robin Rosenberg ()
> >     > Assigned to: Nobody/Anonymous (nobody)
> >     > Summary: Support delta for Double data type
> >     >
> >     > Initial Comment:
> >     > This request is similar to 1961269, but my database contains
> >     DOUBLEs so the DefaultDataTypeFactory ignores my request for
> >     adding deltas
> >     >
> >     >
> >
> ----------------------------------------------------------------------
> >     >
> >     >> Comment By: Jeff Jensen (jeffjensen)
> >     > Date: 2011-08-26 19:34
> >     >
> >     > Message:
> >     > Thanks for the patch!
> >     >
> >     > This is the first I've had a chance to look at it.  So my guess
> >     is others
> >     > haven't had time yet either.
> >     >
> >     > Regretfully, a problem is that it is a git diff instead of a svn
> >     diff.
> >     > Please redo with svn diff so it can apply easily and cleanly.
> >
> >     I'll see what I can do when I get close to the source again, (I used
> >     git-svn to
> >     get the source), but in general "git"  patches are regular diffs
> >     and should
> >     apply with any patch tool. The only significant difference is that
> git
> >     has a prefix
> >     for every path, borrowed from traditional diff/patch usage, while svn
> >     diff does
> >     not add the prefix. patch(1) takes the -p1 argument to remove the
> >     prefix, while
> >     GUI tools usually also have some simple means of removing the prefix.
> >
> >     -- robin
> >
> >     PS!. The tracker item is gone, hence the reply to the mailing list.
> >     >
> >     >
> >
> ----------------------------------------------------------------------
> >     >
> >     > Comment By: Robin Rosenberg ()
> >     > Date: 2011-08-17 17:51
> >     >
> >     > Message:
> >     > Is there a problem with this patch?
> >     >
> >     >
> >
> ----------------------------------------------------------------------
> >     >
> >     > You can respond by visiting:
> >     >
> >
> https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
> >     <
> https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
> >
> >     >
> >     >
> >
> ------------------------------------------------------------------------------
> >     > EMC VNX: the world's simplest storage, starting under $10K
> >     > The only unified storage solution that offers unified management
> >     > Up to 160% more powerful than alternatives and 25% more efficient.
> >     > Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> >     > _______________________________________________
> >     > dbunit-developer mailing list
> >     > dbu...@li...
> >     <mailto:dbu...@li...>
> >     > https://lists.sourceforge.net/lists/listinfo/dbunit-developer
> >
> >
> >
> ------------------------------------------------------------------------------
> >     Doing More with Less: The Next Generation Virtual Desktop
> >     What are the key obstacles that have prevented many mid-market
> >     businesses
> >     from deploying virtual desktops?   How do next-generation virtual
> >     desktops
> >     provide companies an easier-to-deploy, easier-to-manage and more
> >     affordable
> >     virtual desktop model.
> http://www.accelacomm.com/jaw/sfnl/114/51426474/
> >     _______________________________________________
> >     dbunit-developer mailing list
> >     dbu...@li...
> >     <mailto:dbu...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/dbunit-developer
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Doing More with Less: The Next Generation Virtual Desktop
> > What are the key obstacles that have prevented many mid-market businesses
> > from deploying virtual desktops?   How do next-generation virtual
> desktops
> > provide companies an easier-to-deploy, easier-to-manage and more
> affordable
> > virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
> >
> >
> > _______________________________________________
> > dbunit-developer mailing list
> > dbu...@li...
> > https://lists.sourceforge.net/lists/listinfo/dbunit-developer
>
>
>
> ------------------------------------------------------------------------------
> Doing More with Less: The Next Generation Virtual Desktop
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops?   How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
> _______________________________________________
> dbunit-developer mailing list
> dbu...@li...
> https://lists.sourceforge.net/lists/listinfo/dbunit-developer
>

[dbunit-developer] [ dbunit-Feature Requests-3048571 ] Support delta for Double data type

[SourceForge.net <no...@so...>]

Feature Requests item #3048571, was opened at 2010-08-19 05:14
Message generated for change (Settings changed) made by jeffjensen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449494&aid=3048571&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Robin Rosenberg ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Support delta for Double data type

Initial Comment:
This request is similar to 1961269, but my database contains DOUBLEs so the DefaultDataTypeFactory ignores my request for adding deltas

----------------------------------------------------------------------

Comment By: matthias g (gommma)
Date: 2011-08-27 03:25

Message:
I had a quick look at it. At a first glance I can only see that there´'s
some copy/paste from the NumberDataType and I'm wondering whether it is
possible to reuse this class (inherit from NumberDataType).
cheers
matthias 

----------------------------------------------------------------------

Comment By: Jeff Jensen (jeffjensen)
Date: 2011-08-26 19:34

Message:
Thanks for the patch!

This is the first I've had a chance to look at it.  So my guess is others
haven't had time yet either.

Regretfully, a problem is that it is a git diff instead of a svn diff. 
Please redo with svn diff so it can apply easily and cleanly.


----------------------------------------------------------------------

Comment By: Robin Rosenberg ()
Date: 2011-08-17 17:51

Message:
Is there a problem with this patch?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449494&aid=3048571&group_id=47439

Re: [dbunit-developer] [ dbunit-Patches-3048571 ] Support delta for Double data type

[Robin R. <rob...@gm...>]

Jeff Jensen skrev 2011-09-08 20.06:
> Sorry - I moved the entry to the patch tracker.  You'll find it there...
>
Do you have a link? I looked in the Bugs and Feature request trackers 
and these are the only trackers
I see under the dbunit project.

> Eclipse's svn patch tool does not recognize git (and please show me 
> how to make it do so if you know how!).
Subclipe or subversion?

Eclipse standard patch tool (non-team provider specifik)  understands 
unidiff patches,  including the ones
produced by git (as long as extensions aren't used, and I'm pretty sure 
I didn't use any because none were needed).
Of course it ignores the comment/author stuff so I guess it's less 
convenient.

-- robin
> On Thu, Sep 8, 2011 at 9:14 AM, Robin Rosenberg 
> <rob...@gm... <mailto:rob...@gm...>> wrote:
>
>     SourceForge.net skrev 2011-08-27 02.34:
>     > Patches item #3048571, was opened at 2010-08-19 05:14
>     > Message generated for change (Comment added) made by jeffjensen
>     > You can respond by visiting:
>     >
>     https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
>     <https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439>
>     >
>     > Please note that this message will contain a full copy of the
>     comment thread,
>     > including the initial issue submission, for this request,
>     > not just the latest update.
>     > Category: None
>     > Group: None
>     > Status: Open
>     > Resolution: None
>     > Priority: 5
>     > Private: No
>     > Submitted By: Robin Rosenberg ()
>     > Assigned to: Nobody/Anonymous (nobody)
>     > Summary: Support delta for Double data type
>     >
>     > Initial Comment:
>     > This request is similar to 1961269, but my database contains
>     DOUBLEs so the DefaultDataTypeFactory ignores my request for
>     adding deltas
>     >
>     >
>     ----------------------------------------------------------------------
>     >
>     >> Comment By: Jeff Jensen (jeffjensen)
>     > Date: 2011-08-26 19:34
>     >
>     > Message:
>     > Thanks for the patch!
>     >
>     > This is the first I've had a chance to look at it.  So my guess
>     is others
>     > haven't had time yet either.
>     >
>     > Regretfully, a problem is that it is a git diff instead of a svn
>     diff.
>     > Please redo with svn diff so it can apply easily and cleanly.
>
>     I'll see what I can do when I get close to the source again, (I used
>     git-svn to
>     get the source), but in general "git"  patches are regular diffs
>     and should
>     apply with any patch tool. The only significant difference is that git
>     has a prefix
>     for every path, borrowed from traditional diff/patch usage, while svn
>     diff does
>     not add the prefix. patch(1) takes the -p1 argument to remove the
>     prefix, while
>     GUI tools usually also have some simple means of removing the prefix.
>
>     -- robin
>
>     PS!. The tracker item is gone, hence the reply to the mailing list.
>     >
>     >
>     ----------------------------------------------------------------------
>     >
>     > Comment By: Robin Rosenberg ()
>     > Date: 2011-08-17 17:51
>     >
>     > Message:
>     > Is there a problem with this patch?
>     >
>     >
>     ----------------------------------------------------------------------
>     >
>     > You can respond by visiting:
>     >
>     https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
>     <https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439>
>     >
>     >
>     ------------------------------------------------------------------------------
>     > EMC VNX: the world's simplest storage, starting under $10K
>     > The only unified storage solution that offers unified management
>     > Up to 160% more powerful than alternatives and 25% more efficient.
>     > Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
>     > _______________________________________________
>     > dbunit-developer mailing list
>     > dbu...@li...
>     <mailto:dbu...@li...>
>     > https://lists.sourceforge.net/lists/listinfo/dbunit-developer
>
>
>     ------------------------------------------------------------------------------
>     Doing More with Less: The Next Generation Virtual Desktop
>     What are the key obstacles that have prevented many mid-market
>     businesses
>     from deploying virtual desktops?   How do next-generation virtual
>     desktops
>     provide companies an easier-to-deploy, easier-to-manage and more
>     affordable
>     virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
>     _______________________________________________
>     dbunit-developer mailing list
>     dbu...@li...
>     <mailto:dbu...@li...>
>     https://lists.sourceforge.net/lists/listinfo/dbunit-developer
>
>
>
>
> ------------------------------------------------------------------------------
> Doing More with Less: The Next Generation Virtual Desktop
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops?   How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
>
>
> _______________________________________________
> dbunit-developer mailing list
> dbu...@li...
> https://lists.sourceforge.net/lists/listinfo/dbunit-developer

Re: [dbunit-developer] [ dbunit-Patches-3048571 ] Support delta for Double data type

[Jeff J. <jj...@ap...>]

Sorry - I moved the entry to the patch tracker.  You'll find it there...

Eclipse's svn patch tool does not recognize git (and please show me how to
make it do so if you know how!).


On Thu, Sep 8, 2011 at 9:14 AM, Robin Rosenberg
<rob...@gm...>wrote:

> SourceForge.net skrev 2011-08-27 02.34:
> > Patches item #3048571, was opened at 2010-08-19 05:14
> > Message generated for change (Comment added) made by jeffjensen
> > You can respond by visiting:
> >
> https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
> >
> > Please note that this message will contain a full copy of the comment
> thread,
> > including the initial issue submission, for this request,
> > not just the latest update.
> > Category: None
> > Group: None
> > Status: Open
> > Resolution: None
> > Priority: 5
> > Private: No
> > Submitted By: Robin Rosenberg ()
> > Assigned to: Nobody/Anonymous (nobody)
> > Summary: Support delta for Double data type
> >
> > Initial Comment:
> > This request is similar to 1961269, but my database contains DOUBLEs so
> the DefaultDataTypeFactory ignores my request for adding deltas
> >
> > ----------------------------------------------------------------------
> >
> >> Comment By: Jeff Jensen (jeffjensen)
> > Date: 2011-08-26 19:34
> >
> > Message:
> > Thanks for the patch!
> >
> > This is the first I've had a chance to look at it.  So my guess is others
> > haven't had time yet either.
> >
> > Regretfully, a problem is that it is a git diff instead of a svn diff.
> > Please redo with svn diff so it can apply easily and cleanly.
>
> I'll see what I can do when I get close to the source again, (I used
> git-svn to
> get the source), but in general "git"  patches are regular diffs and should
> apply with any patch tool. The only significant difference is that git
> has a prefix
> for every path, borrowed from traditional diff/patch usage, while svn
> diff does
> not add the prefix. patch(1) takes the -p1 argument to remove the
> prefix, while
> GUI tools usually also have some simple means of removing the prefix.
>
> -- robin
>
> PS!. The tracker item is gone, hence the reply to the mailing list.
> >
> > ----------------------------------------------------------------------
> >
> > Comment By: Robin Rosenberg ()
> > Date: 2011-08-17 17:51
> >
> > Message:
> > Is there a problem with this patch?
> >
> > ----------------------------------------------------------------------
> >
> > You can respond by visiting:
> >
> https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
> >
> >
> ------------------------------------------------------------------------------
> > EMC VNX: the world's simplest storage, starting under $10K
> > The only unified storage solution that offers unified management
> > Up to 160% more powerful than alternatives and 25% more efficient.
> > Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> > _______________________________________________
> > dbunit-developer mailing list
> > dbu...@li...
> > https://lists.sourceforge.net/lists/listinfo/dbunit-developer
>
>
>
> ------------------------------------------------------------------------------
> Doing More with Less: The Next Generation Virtual Desktop
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops?   How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
> _______________________________________________
> dbunit-developer mailing list
> dbu...@li...
> https://lists.sourceforge.net/lists/listinfo/dbunit-developer
>

Re: [dbunit-developer] [ dbunit-Patches-3048571 ] Support delta for Double data type

[Robin R. <rob...@gm...>]

SourceForge.net skrev 2011-08-27 02.34:
> Patches item #3048571, was opened at 2010-08-19 05:14
> Message generated for change (Comment added) made by jeffjensen
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
>
> Please note that this message will contain a full copy of the comment thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: None
> Group: None
> Status: Open
> Resolution: None
> Priority: 5
> Private: No
> Submitted By: Robin Rosenberg ()
> Assigned to: Nobody/Anonymous (nobody)
> Summary: Support delta for Double data type
>
> Initial Comment:
> This request is similar to 1961269, but my database contains DOUBLEs so the DefaultDataTypeFactory ignores my request for adding deltas
>
> ----------------------------------------------------------------------
>
>> Comment By: Jeff Jensen (jeffjensen)
> Date: 2011-08-26 19:34
>
> Message:
> Thanks for the patch!
>
> This is the first I've had a chance to look at it.  So my guess is others
> haven't had time yet either.
>
> Regretfully, a problem is that it is a git diff instead of a svn diff.
> Please redo with svn diff so it can apply easily and cleanly.

I'll see what I can do when I get close to the source again, (I used 
git-svn to
get the source), but in general "git"  patches are regular diffs and should
apply with any patch tool. The only significant difference is that git 
has a prefix
for every path, borrowed from traditional diff/patch usage, while svn 
diff does
not add the prefix. patch(1) takes the -p1 argument to remove the 
prefix, while
GUI tools usually also have some simple means of removing the prefix.

-- robin

PS!. The tracker item is gone, hence the reply to the mailing list.
>
> ----------------------------------------------------------------------
>
> Comment By: Robin Rosenberg ()
> Date: 2011-08-17 17:51
>
> Message:
> Is there a problem with this patch?
>
> ----------------------------------------------------------------------
>
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439
>
> ------------------------------------------------------------------------------
> EMC VNX: the world's simplest storage, starting under $10K
> The only unified storage solution that offers unified management
> Up to 160% more powerful than alternatives and 25% more efficient.
> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> _______________________________________________
> dbunit-developer mailing list
> dbu...@li...
> https://lists.sourceforge.net/lists/listinfo/dbunit-developer

[dbunit-developer] [ dbunit-Feature Requests-3405335 ] Reduce FlatXmlProducer memory footprint

[SourceForge.net <no...@so...>]

Feature Requests item #3405335, was opened at 2011-09-07 08:12
Message generated for change (Tracker Item Submitted) made by slandelle
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449494&aid=3405335&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stéphane Landelle (slandelle)
Assigned to: Nobody/Anonymous (nobody)
Summary: Reduce FlatXmlProducer memory footprint

Initial Comment:
I use DbUnit for loading large flat datasets.
Memory footprint is very high because FlatXmlDataSet is a CachedDataSet and it keep all the data in memory.
The problem is that FlatXmlProducer instanciate Columns directly from SAX output, so attribute names and values all always new Strings, even though they might be equal to previously seen data (column names, foreign keys).

Why not use a cache (this behavior could be optional) that would reuse String instances?

I can provide a patch if you're interested.

Sincerely,

Stéphane Landelle

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449494&aid=3405335&group_id=47439

[dbunit-developer] [ dbunit-Patches-3048571 ] Support delta for Double data type

[SourceForge.net <no...@so...>]

Patches item #3048571, was opened at 2010-08-19 10:14
Message generated for change (Comment added) made by gommma
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Robin Rosenberg ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Support delta for Double data type

Initial Comment:
This request is similar to 1961269, but my database contains DOUBLEs so the DefaultDataTypeFactory ignores my request for adding deltas

----------------------------------------------------------------------

>Comment By: matthias g (gommma)
Date: 2011-08-27 08:25

Message:
I had a quick look at it. At a first glance I can only see that there´'s
some copy/paste from the NumberDataType and I'm wondering whether it is
possible to reuse this class (inherit from NumberDataType).
cheers
matthias 

----------------------------------------------------------------------

Comment By: Jeff Jensen (jeffjensen)
Date: 2011-08-27 00:34

Message:
Thanks for the patch!

This is the first I've had a chance to look at it.  So my guess is others
haven't had time yet either.

Regretfully, a problem is that it is a git diff instead of a svn diff. 
Please redo with svn diff so it can apply easily and cleanly.


----------------------------------------------------------------------

Comment By: Robin Rosenberg ()
Date: 2011-08-17 22:51

Message:
Is there a problem with this patch?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439

[dbunit-developer] [ dbunit-Patches-3048571 ] Support delta for Double data type

[SourceForge.net <no...@so...>]

Patches item #3048571, was opened at 2010-08-19 05:14
Message generated for change (Comment added) made by jeffjensen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Robin Rosenberg ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Support delta for Double data type

Initial Comment:
This request is similar to 1961269, but my database contains DOUBLEs so the DefaultDataTypeFactory ignores my request for adding deltas

----------------------------------------------------------------------

>Comment By: Jeff Jensen (jeffjensen)
Date: 2011-08-26 19:34

Message:
Thanks for the patch!

This is the first I've had a chance to look at it.  So my guess is others
haven't had time yet either.

Regretfully, a problem is that it is a git diff instead of a svn diff. 
Please redo with svn diff so it can apply easily and cleanly.


----------------------------------------------------------------------

Comment By: Robin Rosenberg ()
Date: 2011-08-17 17:51

Message:
Is there a problem with this patch?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449493&aid=3048571&group_id=47439

[dbunit-developer] [ dbunit-Feature Requests-3048571 ] Support delta for Double data type

[SourceForge.net <no...@so...>]

Feature Requests item #3048571, was opened at 2010-08-19 10:14
Message generated for change (Comment added) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449494&aid=3048571&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Robin Rosenberg ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Support delta for Double data type

Initial Comment:
This request is similar to 1961269, but my database contains DOUBLEs so the DefaultDataTypeFactory ignores my request for adding deltas

----------------------------------------------------------------------

>Comment By: Robin Rosenberg ()
Date: 2011-08-17 22:51

Message:
Is there a problem with this patch?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449494&aid=3048571&group_id=47439

[dbunit-developer] [ dbunit-Bugs-3392287 ] Wrong comparison with bytes array

[SourceForge.net <no...@so...>]

Bugs item #3392287, was opened at 2011-08-16 10:52
Message generated for change (Comment added) made by khayman44
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3392287&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: v2.2.2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mickael (khayman44)
Assigned to: matthias g (gommma)
Summary: Wrong comparison with bytes array

Initial Comment:
The method Column.compare doesn't work with bytes array. When using expecting dataset with bytes array columns, the comparison always fails. Indeed, calling equals on arrays is the same as using ==. You should either use a list or iterating over the elements.

----------------------------------------------------------------------

>Comment By: Mickael (khayman44)
Date: 2011-08-16 15:08

Message:
I've uploaded test files. I'm sorry but I don't really have time to submit
a fix. I can only tell you that the issue comes from the equals method.

----------------------------------------------------------------------

Comment By: Jeff Jensen (jeffjensen)
Date: 2011-08-16 14:23

Message:
Thanks for reporting this.  Would be great if you attached tests with a
fix... do you have time to?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3392287&group_id=47439

[dbunit-developer] [ dbunit-Bugs-3392287 ] Wrong comparison with bytes array

[SourceForge.net <no...@so...>]

Bugs item #3392287, was opened at 2011-08-16 03:52
Message generated for change (Comment added) made by jeffjensen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3392287&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: v2.2.2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mickael (khayman44)
Assigned to: matthias g (gommma)
Summary: Wrong comparison with bytes array

Initial Comment:
The method Column.compare doesn't work with bytes array. When using expecting dataset with bytes array columns, the comparison always fails. Indeed, calling equals on arrays is the same as using ==. You should either use a list or iterating over the elements.

----------------------------------------------------------------------

>Comment By: Jeff Jensen (jeffjensen)
Date: 2011-08-16 07:23

Message:
Thanks for reporting this.  Would be great if you attached tests with a
fix... do you have time to?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3392287&group_id=47439

[dbunit-developer] [ dbunit-Bugs-3392287 ] Wrong comparison with bytes array

[SourceForge.net <no...@so...>]

Bugs item #3392287, was opened at 2011-08-16 10:52
Message generated for change (Tracker Item Submitted) made by khayman44
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3392287&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: v2.2.2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mickael (khayman44)
Assigned to: matthias g (gommma)
Summary: Wrong comparison with bytes array

Initial Comment:
The method Column.compare doesn't work with bytes array. When using expecting dataset with bytes array columns, the comparison always fails. Indeed, calling equals on arrays is the same as using ==. You should either use a list or iterating over the elements.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3392287&group_id=47439

[dbunit-developer] [ dbunit-Bugs-3378407 ] Can not obtain relations from several columns

[SourceForge.net <no...@so...>]

Bugs item #3378407, was opened at 2011-07-26 12:53
Message generated for change (Tracker Item Submitted) made by marcelpb
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3378407&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Marcel Puchol-Blasco (marcelpb)
Assigned to: matthias g (gommma)
Summary: Can not obtain relations from several columns

Initial Comment:
When you are trying to extract the relationship columns between tables, you can do it using ExportedKeysSearchCallback or ImportedKeysSearchCallback. These two classes extends from AbstractMetaDataBasedSearchCallback, which, in its function 'getNodes' obtains the edges which a table is related.
If we have the following tables

CREATE TABLE test(c1 integer, c2 integer, constaint pk_test primary key(c1, c2));
CREATE TABLE test2(c integer primary key, r1 integer, r2 integer, constaint fk_test2_to_test foreign key(r1,r2) references test(c1,c2));

in which we have several columns related, the function getNodes only obtains the first one. The problem here is that this function stores the result in a SortedSet object, which requires the 'compareTo' function to store the information.  In AbstractMetaDataBasedSearchCallback, the edges are stored using the object ForeignKeyRelationshipEdge, which implements the 'equals' and 'hashCode' functions, but not the 'compareTo'. So, having all this into account, when several columns from the same table are tried to store in the SortedSet object, only the first will be stored, because these objects are compared internally as Edge objects (not as ForeignKeyRelationshipEdge).
To solve this problem only should implement the 'compareTo' function in the ForeignKeyRelationshipEdge class.
Regards.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3378407&group_id=47439

[dbunit-developer] Does DBUnit support DB2 for i v6.1?

[Cherry Y. <che...@gm...>]

Hello all,
I am looking into if it is possible to use DBUnit to work with DB2 for i
v6.1(on AS400)? I did some search and saw that people were using DBUnit with
DB2 z and other type of DB2.

Does anyone know that if DB2 for i v 6.1 is supported in DBUnit?

I appreciate any response.
Clara

BTW, I posted this to user mailing list and got no response. So trying my
luck here while I am debugging my DBUnit Tests against DB2 for i.

[dbunit-developer] [ dbunit-Bugs-3358500 ] NoSuchTableException when working on multi-schema database

[SourceForge.net <no...@so...>]

Bugs item #3358500, was opened at 2011-07-08 10:08
Message generated for change (Comment added) made by jeffjensen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3358500&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: v2.4.*
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: enji (njouffre)
>Assigned to: Jeff Jensen (jeffjensen)
Summary: NoSuchTableException when working on multi-schema database

Initial Comment:
Hi,

Environment : Unitils 3.1, DbUnit 2.4.3, MySQL database
Test case : crash when unitils try to insert data using xml dataset before running a test
Stack trace :

Caused by: org.dbunit.dataset.NoSuchTableException: my_table_in_second_schema
	at org.dbunit.database.DatabaseDataSet.getTableMetaData(DatabaseDataSet.java:278)
	at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:109)
	at org.dbunit.operation.CompositeOperation.execute(CompositeOperation.java:79)
	at org.unitils.dbunit.datasetloadstrategy.impl.CleanInsertLoadStrategy.doExecute(CleanInsertLoadStrategy.java:45)
	at org.unitils.dbunit.datasetloadstrategy.impl.BaseDataSetLoadStrategy.execute(BaseDataSetLoadStrategy.java:44)
	... 20 more

Explanation : this bug is due to the way mysql implement catalog, schema and database notions to some "illogical" compatibility reasons
see http://forums.mysql.com/read.php?39,137564,137564
in several dbunit methods, parameter catalog is passed as null when trying to retrieve tables, columns or primary keys from DatabaseMetaData object

Bug fix :

in org.dbunit.util.SQLHelper add method

public static boolean isMySQLDb(DatabaseMetaData metaData) throws SQLException 
{
        String dbProductName = metaData.getDatabaseProductName();
        boolean isMySQL = (dbProductName != null && dbProductName.equals(DB_PRODUCT_MYSQL));
        return isMySQL;
}

in org.dbunit.database.DatabaseDataSet modify method initialize()

            Connection jdbcConnection = _connection.getConnection();
            DatabaseMetaData databaseMetaData = jdbcConnection.getMetaData();

            String schema = _connection.getSchema();
            
            if(SQLHelper.isSybaseDb(jdbcConnection.getMetaData()) && !jdbcConnection.getMetaData().getUserName().equals(schema) ){
                logger.warn("For sybase the schema name should be equal to the user name. " +
                		"Otherwise the DatabaseMetaData#getTables() method might not return any columns. " +
                		"See dbunit tracker #1628896 and http://issues.apache.org/jira/browse/TORQUE-40?page=all");
            }
            
            // Bug fix specific when using MySQL SGBD
            // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
            String catalog = null;
            if (SQLHelper.isMySQLDb(databaseMetaData)) {
            	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
                		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
                		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
            	catalog = schema;
            }
            
            DatabaseConfig config = _connection.getConfig();
            String[] tableType = (String[])config.getProperty(DatabaseConfig.PROPERTY_TABLE_TYPE);

            ResultSet resultSet = databaseMetaData.getTables(
            		catalog, schema, "%", tableType);
			
	    // end bug fix

in org.dbunit.database.DatabaseDataSet.DatabaseTableMetaData modify method getPrimaryKeyNames()

        Connection connection = _connection.getConnection();
        DatabaseMetaData databaseMetaData = connection.getMetaData();
        
        // Bug fix specific when using MySQL SGBD
        // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
        String catalog = null;
        if (SQLHelper.isMySQLDb(databaseMetaData)) {
        	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
            		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
            		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
        	catalog = schemaName;
        }
                
        ResultSet resultSet = databaseMetaData.getPrimaryKeys(
        		catalog, schemaName, tableName);
        // end bug fix	

in org.dbunit.database.DatabaseDataSet.DatabaseTableMetaData modify method tableExists(DatabaseMetaData metaData, String schema, String tableName) 		

        // Bug fix specific when using MySQL SGBD
        // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
        String catalog = null;
        if (SQLHelper.isMySQLDb(metaData)) {
        	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
            		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
            		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
        	catalog = schema;
        }
        
    	ResultSet tableRs = metaData.getTables(catalog, schema, tableName, null);
    	// end bug fix	

Until know I found only theses 3 pieces of code where catalog parameter was required to make it work with MySQL database, but I'm not sure they are the only ones.

----------------------------------------------------------------------

>Comment By: Jeff Jensen (jeffjensen)
Date: 2011-07-08 13:09

Message:
Great, glad 2.4.8 took care of that issue... thought it would.
I'm closing this issue as the problem no longer exists.  Please open
another entry as needed for new ones.

----------------------------------------------------------------------

Comment By: enji (njouffre)
Date: 2011-07-08 11:11

Message:
I tried with 2.4.8, which fixred this NoSuchTableException, but I'm now
stucked with another bug, a unitils one this time.
I'll try to commit the changes as soon as possible.

----------------------------------------------------------------------

Comment By: Jeff Jensen (jeffjensen)
Date: 2011-07-08 11:06

Message:
I just noticed the "DbUnit 2.4.3" - are you able to try with 2.4.8, or even
better, 2.4.9-snapshot (build from source)?  There have been some changes
since 2.4.3 that may help, particularly a bug I fixed with multiple schemas
(name was not always used).


----------------------------------------------------------------------

Comment By: Jeff Jensen (jeffjensen)
Date: 2011-07-08 11:03

Message:
Thank you for sharing this.  It will be much easier, clearer, and accurate
to commit the changes if you would make an svn patch file and attach.  Are
you able to do that?

Additionally, it's difficult to verify/know this is correct changes
without tests.  You have much higher chance of having the patch applied
with tests included.  Are you able to make tests to prove the behavior
(particularly, fails without it)?

Thanks again...


----------------------------------------------------------------------

Comment By: enji (njouffre)
Date: 2011-07-08 10:40

Message:
sorry, I copy/paste wrong things in my post
the last bug fix is correct bug method tableExists() is in
org.dbunit.util.SQLHelper
and method getPrimaryKeyNames in org.dbunit.database.DatabaseTableMetaData

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3358500&group_id=47439

[dbunit-developer] [ dbunit-Bugs-3358500 ] NoSuchTableException when working on multi-schema database

[SourceForge.net <no...@so...>]

Bugs item #3358500, was opened at 2011-07-08 17:08
Message generated for change (Comment added) made by njouffre
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3358500&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: v2.4.*
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: enji (njouffre)
Assigned to: matthias g (gommma)
Summary: NoSuchTableException when working on multi-schema database

Initial Comment:
Hi,

Environment : Unitils 3.1, DbUnit 2.4.3, MySQL database
Test case : crash when unitils try to insert data using xml dataset before running a test
Stack trace :

Caused by: org.dbunit.dataset.NoSuchTableException: my_table_in_second_schema
	at org.dbunit.database.DatabaseDataSet.getTableMetaData(DatabaseDataSet.java:278)
	at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:109)
	at org.dbunit.operation.CompositeOperation.execute(CompositeOperation.java:79)
	at org.unitils.dbunit.datasetloadstrategy.impl.CleanInsertLoadStrategy.doExecute(CleanInsertLoadStrategy.java:45)
	at org.unitils.dbunit.datasetloadstrategy.impl.BaseDataSetLoadStrategy.execute(BaseDataSetLoadStrategy.java:44)
	... 20 more

Explanation : this bug is due to the way mysql implement catalog, schema and database notions to some "illogical" compatibility reasons
see http://forums.mysql.com/read.php?39,137564,137564
in several dbunit methods, parameter catalog is passed as null when trying to retrieve tables, columns or primary keys from DatabaseMetaData object

Bug fix :

in org.dbunit.util.SQLHelper add method

public static boolean isMySQLDb(DatabaseMetaData metaData) throws SQLException 
{
        String dbProductName = metaData.getDatabaseProductName();
        boolean isMySQL = (dbProductName != null && dbProductName.equals(DB_PRODUCT_MYSQL));
        return isMySQL;
}

in org.dbunit.database.DatabaseDataSet modify method initialize()

            Connection jdbcConnection = _connection.getConnection();
            DatabaseMetaData databaseMetaData = jdbcConnection.getMetaData();

            String schema = _connection.getSchema();
            
            if(SQLHelper.isSybaseDb(jdbcConnection.getMetaData()) && !jdbcConnection.getMetaData().getUserName().equals(schema) ){
                logger.warn("For sybase the schema name should be equal to the user name. " +
                		"Otherwise the DatabaseMetaData#getTables() method might not return any columns. " +
                		"See dbunit tracker #1628896 and http://issues.apache.org/jira/browse/TORQUE-40?page=all");
            }
            
            // Bug fix specific when using MySQL SGBD
            // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
            String catalog = null;
            if (SQLHelper.isMySQLDb(databaseMetaData)) {
            	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
                		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
                		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
            	catalog = schema;
            }
            
            DatabaseConfig config = _connection.getConfig();
            String[] tableType = (String[])config.getProperty(DatabaseConfig.PROPERTY_TABLE_TYPE);

            ResultSet resultSet = databaseMetaData.getTables(
            		catalog, schema, "%", tableType);
			
	    // end bug fix

in org.dbunit.database.DatabaseDataSet.DatabaseTableMetaData modify method getPrimaryKeyNames()

        Connection connection = _connection.getConnection();
        DatabaseMetaData databaseMetaData = connection.getMetaData();
        
        // Bug fix specific when using MySQL SGBD
        // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
        String catalog = null;
        if (SQLHelper.isMySQLDb(databaseMetaData)) {
        	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
            		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
            		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
        	catalog = schemaName;
        }
                
        ResultSet resultSet = databaseMetaData.getPrimaryKeys(
        		catalog, schemaName, tableName);
        // end bug fix	

in org.dbunit.database.DatabaseDataSet.DatabaseTableMetaData modify method tableExists(DatabaseMetaData metaData, String schema, String tableName) 		

        // Bug fix specific when using MySQL SGBD
        // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
        String catalog = null;
        if (SQLHelper.isMySQLDb(metaData)) {
        	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
            		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
            		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
        	catalog = schema;
        }
        
    	ResultSet tableRs = metaData.getTables(catalog, schema, tableName, null);
    	// end bug fix	

Until know I found only theses 3 pieces of code where catalog parameter was required to make it work with MySQL database, but I'm not sure they are the only ones.

----------------------------------------------------------------------

>Comment By: enji (njouffre)
Date: 2011-07-08 18:11

Message:
I tried with 2.4.8, which fixred this NoSuchTableException, but I'm now
stucked with another bug, a unitils one this time.
I'll try to commit the changes as soon as possible.

----------------------------------------------------------------------

Comment By: Jeff Jensen (jeffjensen)
Date: 2011-07-08 18:06

Message:
I just noticed the "DbUnit 2.4.3" - are you able to try with 2.4.8, or even
better, 2.4.9-snapshot (build from source)?  There have been some changes
since 2.4.3 that may help, particularly a bug I fixed with multiple schemas
(name was not always used).


----------------------------------------------------------------------

Comment By: Jeff Jensen (jeffjensen)
Date: 2011-07-08 18:03

Message:
Thank you for sharing this.  It will be much easier, clearer, and accurate
to commit the changes if you would make an svn patch file and attach.  Are
you able to do that?

Additionally, it's difficult to verify/know this is correct changes
without tests.  You have much higher chance of having the patch applied
with tests included.  Are you able to make tests to prove the behavior
(particularly, fails without it)?

Thanks again...


----------------------------------------------------------------------

Comment By: enji (njouffre)
Date: 2011-07-08 17:40

Message:
sorry, I copy/paste wrong things in my post
the last bug fix is correct bug method tableExists() is in
org.dbunit.util.SQLHelper
and method getPrimaryKeyNames in org.dbunit.database.DatabaseTableMetaData

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3358500&group_id=47439

[dbunit-developer] [ dbunit-Bugs-3358500 ] NoSuchTableException when working on multi-schema database

[SourceForge.net <no...@so...>]

Bugs item #3358500, was opened at 2011-07-08 10:08
Message generated for change (Comment added) made by jeffjensen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3358500&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: v2.4.*
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: enji (njouffre)
Assigned to: matthias g (gommma)
Summary: NoSuchTableException when working on multi-schema database

Initial Comment:
Hi,

Environment : Unitils 3.1, DbUnit 2.4.3, MySQL database
Test case : crash when unitils try to insert data using xml dataset before running a test
Stack trace :

Caused by: org.dbunit.dataset.NoSuchTableException: my_table_in_second_schema
	at org.dbunit.database.DatabaseDataSet.getTableMetaData(DatabaseDataSet.java:278)
	at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:109)
	at org.dbunit.operation.CompositeOperation.execute(CompositeOperation.java:79)
	at org.unitils.dbunit.datasetloadstrategy.impl.CleanInsertLoadStrategy.doExecute(CleanInsertLoadStrategy.java:45)
	at org.unitils.dbunit.datasetloadstrategy.impl.BaseDataSetLoadStrategy.execute(BaseDataSetLoadStrategy.java:44)
	... 20 more

Explanation : this bug is due to the way mysql implement catalog, schema and database notions to some "illogical" compatibility reasons
see http://forums.mysql.com/read.php?39,137564,137564
in several dbunit methods, parameter catalog is passed as null when trying to retrieve tables, columns or primary keys from DatabaseMetaData object

Bug fix :

in org.dbunit.util.SQLHelper add method

public static boolean isMySQLDb(DatabaseMetaData metaData) throws SQLException 
{
        String dbProductName = metaData.getDatabaseProductName();
        boolean isMySQL = (dbProductName != null && dbProductName.equals(DB_PRODUCT_MYSQL));
        return isMySQL;
}

in org.dbunit.database.DatabaseDataSet modify method initialize()

            Connection jdbcConnection = _connection.getConnection();
            DatabaseMetaData databaseMetaData = jdbcConnection.getMetaData();

            String schema = _connection.getSchema();
            
            if(SQLHelper.isSybaseDb(jdbcConnection.getMetaData()) && !jdbcConnection.getMetaData().getUserName().equals(schema) ){
                logger.warn("For sybase the schema name should be equal to the user name. " +
                		"Otherwise the DatabaseMetaData#getTables() method might not return any columns. " +
                		"See dbunit tracker #1628896 and http://issues.apache.org/jira/browse/TORQUE-40?page=all");
            }
            
            // Bug fix specific when using MySQL SGBD
            // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
            String catalog = null;
            if (SQLHelper.isMySQLDb(databaseMetaData)) {
            	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
                		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
                		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
            	catalog = schema;
            }
            
            DatabaseConfig config = _connection.getConfig();
            String[] tableType = (String[])config.getProperty(DatabaseConfig.PROPERTY_TABLE_TYPE);

            ResultSet resultSet = databaseMetaData.getTables(
            		catalog, schema, "%", tableType);
			
	    // end bug fix

in org.dbunit.database.DatabaseDataSet.DatabaseTableMetaData modify method getPrimaryKeyNames()

        Connection connection = _connection.getConnection();
        DatabaseMetaData databaseMetaData = connection.getMetaData();
        
        // Bug fix specific when using MySQL SGBD
        // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
        String catalog = null;
        if (SQLHelper.isMySQLDb(databaseMetaData)) {
        	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
            		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
            		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
        	catalog = schemaName;
        }
                
        ResultSet resultSet = databaseMetaData.getPrimaryKeys(
        		catalog, schemaName, tableName);
        // end bug fix	

in org.dbunit.database.DatabaseDataSet.DatabaseTableMetaData modify method tableExists(DatabaseMetaData metaData, String schema, String tableName) 		

        // Bug fix specific when using MySQL SGBD
        // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
        String catalog = null;
        if (SQLHelper.isMySQLDb(metaData)) {
        	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
            		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
            		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
        	catalog = schema;
        }
        
    	ResultSet tableRs = metaData.getTables(catalog, schema, tableName, null);
    	// end bug fix	

Until know I found only theses 3 pieces of code where catalog parameter was required to make it work with MySQL database, but I'm not sure they are the only ones.

----------------------------------------------------------------------

>Comment By: Jeff Jensen (jeffjensen)
Date: 2011-07-08 11:06

Message:
I just noticed the "DbUnit 2.4.3" - are you able to try with 2.4.8, or even
better, 2.4.9-snapshot (build from source)?  There have been some changes
since 2.4.3 that may help, particularly a bug I fixed with multiple schemas
(name was not always used).


----------------------------------------------------------------------

Comment By: Jeff Jensen (jeffjensen)
Date: 2011-07-08 11:03

Message:
Thank you for sharing this.  It will be much easier, clearer, and accurate
to commit the changes if you would make an svn patch file and attach.  Are
you able to do that?

Additionally, it's difficult to verify/know this is correct changes
without tests.  You have much higher chance of having the patch applied
with tests included.  Are you able to make tests to prove the behavior
(particularly, fails without it)?

Thanks again...


----------------------------------------------------------------------

Comment By: enji (njouffre)
Date: 2011-07-08 10:40

Message:
sorry, I copy/paste wrong things in my post
the last bug fix is correct bug method tableExists() is in
org.dbunit.util.SQLHelper
and method getPrimaryKeyNames in org.dbunit.database.DatabaseTableMetaData

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3358500&group_id=47439

[dbunit-developer] [ dbunit-Bugs-3358500 ] NoSuchTableException when working on multi-schema database

[SourceForge.net <no...@so...>]

Bugs item #3358500, was opened at 2011-07-08 10:08
Message generated for change (Comment added) made by jeffjensen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3358500&group_id=47439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Bug
Group: v2.4.*
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: enji (njouffre)
Assigned to: matthias g (gommma)
Summary: NoSuchTableException when working on multi-schema database

Initial Comment:
Hi,

Environment : Unitils 3.1, DbUnit 2.4.3, MySQL database
Test case : crash when unitils try to insert data using xml dataset before running a test
Stack trace :

Caused by: org.dbunit.dataset.NoSuchTableException: my_table_in_second_schema
	at org.dbunit.database.DatabaseDataSet.getTableMetaData(DatabaseDataSet.java:278)
	at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:109)
	at org.dbunit.operation.CompositeOperation.execute(CompositeOperation.java:79)
	at org.unitils.dbunit.datasetloadstrategy.impl.CleanInsertLoadStrategy.doExecute(CleanInsertLoadStrategy.java:45)
	at org.unitils.dbunit.datasetloadstrategy.impl.BaseDataSetLoadStrategy.execute(BaseDataSetLoadStrategy.java:44)
	... 20 more

Explanation : this bug is due to the way mysql implement catalog, schema and database notions to some "illogical" compatibility reasons
see http://forums.mysql.com/read.php?39,137564,137564
in several dbunit methods, parameter catalog is passed as null when trying to retrieve tables, columns or primary keys from DatabaseMetaData object

Bug fix :

in org.dbunit.util.SQLHelper add method

public static boolean isMySQLDb(DatabaseMetaData metaData) throws SQLException 
{
        String dbProductName = metaData.getDatabaseProductName();
        boolean isMySQL = (dbProductName != null && dbProductName.equals(DB_PRODUCT_MYSQL));
        return isMySQL;
}

in org.dbunit.database.DatabaseDataSet modify method initialize()

            Connection jdbcConnection = _connection.getConnection();
            DatabaseMetaData databaseMetaData = jdbcConnection.getMetaData();

            String schema = _connection.getSchema();
            
            if(SQLHelper.isSybaseDb(jdbcConnection.getMetaData()) && !jdbcConnection.getMetaData().getUserName().equals(schema) ){
                logger.warn("For sybase the schema name should be equal to the user name. " +
                		"Otherwise the DatabaseMetaData#getTables() method might not return any columns. " +
                		"See dbunit tracker #1628896 and http://issues.apache.org/jira/browse/TORQUE-40?page=all");
            }
            
            // Bug fix specific when using MySQL SGBD
            // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
            String catalog = null;
            if (SQLHelper.isMySQLDb(databaseMetaData)) {
            	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
                		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
                		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
            	catalog = schema;
            }
            
            DatabaseConfig config = _connection.getConfig();
            String[] tableType = (String[])config.getProperty(DatabaseConfig.PROPERTY_TABLE_TYPE);

            ResultSet resultSet = databaseMetaData.getTables(
            		catalog, schema, "%", tableType);
			
	    // end bug fix

in org.dbunit.database.DatabaseDataSet.DatabaseTableMetaData modify method getPrimaryKeyNames()

        Connection connection = _connection.getConnection();
        DatabaseMetaData databaseMetaData = connection.getMetaData();
        
        // Bug fix specific when using MySQL SGBD
        // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
        String catalog = null;
        if (SQLHelper.isMySQLDb(databaseMetaData)) {
        	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
            		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
            		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
        	catalog = schemaName;
        }
                
        ResultSet resultSet = databaseMetaData.getPrimaryKeys(
        		catalog, schemaName, tableName);
        // end bug fix	

in org.dbunit.database.DatabaseDataSet.DatabaseTableMetaData modify method tableExists(DatabaseMetaData metaData, String schema, String tableName) 		

        // Bug fix specific when using MySQL SGBD
        // see http://forums.mysql.com/read.php?39,137564,137564#msg-137564
        String catalog = null;
        if (SQLHelper.isMySQLDb(metaData)) {
        	logger.warn("For MySQL the catalog name should not be null. It should be equal to the schema name. " +
            		"Otherwise the DatabaseMetaData#getTables() method might not return any columns when testing multiple schema database. " +
            		"See http://forums.mysql.com/read.php?39,137564,137564#msg-137564");
        	catalog = schema;
        }
        
    	ResultSet tableRs = metaData.getTables(catalog, schema, tableName, null);
    	// end bug fix	

Until know I found only theses 3 pieces of code where catalog parameter was required to make it work with MySQL database, but I'm not sure they are the only ones.

----------------------------------------------------------------------

>Comment By: Jeff Jensen (jeffjensen)
Date: 2011-07-08 11:03

Message:
Thank you for sharing this.  It will be much easier, clearer, and accurate
to commit the changes if you would make an svn patch file and attach.  Are
you able to do that?

Additionally, it's difficult to verify/know this is correct changes
without tests.  You have much higher chance of having the patch applied
with tests included.  Are you able to make tests to prove the behavior
(particularly, fails without it)?

Thanks again...


----------------------------------------------------------------------

Comment By: enji (njouffre)
Date: 2011-07-08 10:40

Message:
sorry, I copy/paste wrong things in my post
the last bug fix is correct bug method tableExists() is in
org.dbunit.util.SQLHelper
and method getPrimaryKeyNames in org.dbunit.database.DatabaseTableMetaData

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=449491&aid=3358500&group_id=47439