Hi, See:
http://my.cdash.org/viewTest.php?buildid=40388 http://my.cdash.org/viewTest.php?buildid=40389 I am fight with double tests and null strings. I created the length member to struct FIELDINFO and create some special fields like '_*' which help to test some string functions. Please show me your idea about: "rearrange the code in test_dbi.c to separate driver-specific code from non-specific code". In the test framework exists some tests written to specific driver like: if (mysql) do... else if (pgsql) do... The accessors functions and struct FIELDINFO helps to reduces it. I will setup my environment to test mysql, pgsql and firebird. But I think it is not will be a problem. Thanks. -- ----------------------------------------------------------- João Henrique Freitas - joaohf_at_gmail.com Campinas-SP-Brasil BSD051283 LPI 1 http://www.joaohfreitas.eti.br ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ libdbi-devel mailing list libdbi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-devel
