Markus Hoenicka writes: > I'm sorry, I have to correct myself. It is the number of *columns* > which is reported incorrectly, not the number of *rows*. Any > reasonable application won't care about the number of columns if you > don't get back a single row. The incorrect column issue is just > something which is not supposed to happen, and I want to see it fixed > before doing another release.
I've checked this problem again. It appears now that the new test framework had a bug in this particular test in that it assumed the number of fields had to be 0 if a query returned zero rows. In fact, this is not the case in most database engines. At least MySQL, PostgreSQL, SQLite3, and Firebird return the requested number of fields even if no rows are returned. SQLite returns 0 which is apparently a feature of the 2.x series of SQLite. I can't comment on the other engines at this time. So all we need to do on this issue is to fix the test :-/ regards, Markus -- Markus Hoenicka markus.hoeni...@cats.de (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Libdbi-drivers-devel mailing list Libdbi-drivers-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel
