Hello Many thanks for the reporting...
> > 1) a typo in ask_for_conninfo() garbled the logic of the connection > settings dialog. Specifically, the program wouldn't ask for the > database directory when testing the firebird driver, causing it to > fail. I've reverted an "else if" to "if" to fix this, see revision > 1.1.2.4 of test_dbi_cgreen.c. Also, there was a superfluous "else" > which would affect engines that do not use database directories, see > revision 1.1.2.5. > Ok. > 2) testing the return values of functions which retrieve floating > point numbers is doomed to fail due to rounding errors. Is there a way > to express "is approximately equal to" as opposed to "equals" in > cgreen? If not, we'd have to compute mantissa and exponent of the > input and output values and compare these integers with reasonable > precision. > Not yet. But I can create a assert approximately_equal_to() in Cgreen framework. I need to think about this a bit. > 4) the mysql test runs clean except for the test_retrieve_zero_rows > test which we talked about previously. Please see the last revision. I fixed the test_retrieve_zero_rows() test and applied an assert for each engine. In my test, the mysql have 25 rows. Old test_dbi have 26. Now the new framework with mysql test reports: Completed "libdbi framework test": 338 passes, 0 failures, 0 exceptions. Obs.: The 338 is because I made a cleanup in some unnecessary asserts. > 3) testing the firebird driver is a PITA. The old test code runs to > completion except for the final "DROP TABLE" test. The new test code > triggers a "Fatal lock manager error: invalid lock id (XXXXX), errno: > 83" error on my platform. According to what Google says this is a > Firebird bug which has been fixed only recently in version 2.5. Did > you have a chance to test the firebird driver? > > > 5) pgsql complains about 'type "e" does not exist' when inserting data > into the table. This is apparently caused by the strings which you use > to fill the blob fields. What is the leading non-quoted 'E' intended > for? > > 6) sqlite and sqlite 3 report 6 failures. Two stem from the > test_dbi_result_field_is_null(_idx) tests which may actually indicate > driver bugs. I'll look into that. The remainder are the problems > mentioned above. > I have tested firebird some time ago. I need to test again. The some for sqlite and pgsql. I will do it in this week. Thanks -- ----------------------------------------------------------- João Henrique Freitas - joaohf_at_gmail.com Campinas-SP-Brasil BSD051283 LPI 1 http://www.joaohfreitas.eti.br ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Libdbi-drivers-devel mailing list Libdbi-drivers-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel
