Re: cvs: pear /MDB2/tests MDB2_usage_testcase.php
| From: | Lukas Kahwe Smith | Date: | Sun, 20 Aug 2006 12:13:14 +0000 |
| Subject: | Re: cvs: pear /MDB2/tests MDB2_usage_testcase.php | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43741@lists.php.net to get a copy of this message | ||
Lukas Kahwe Smith wrote:
Justin Patrin wrote:In order to end another monolog of mine on MDB2: I have pondered some more .. and users that want to find out what breaks if they disable portability options, they can just specify the given portability setting in their test_setup.php regards, LukasThere is the question of how to deal with test cases that essentially just illustrate the default behavior of the given RDBMS without any portability handling. Obviously these tests may fail even though there is nothing broken in the driver, simply because the RDBMS works differently by default as is expected in MDB2 for maximum portability. Leaving them in has the advantage that users can better realize what it means if they disable the given portability setting. But has the disadvantage of potentially confusing users that the driver is broken. I am sort of unsure how to approach this. Maybe the better solution would be to remove tests with the portability settings disabled and instead work towards documenting this inside the manual. However someone would need to add this documentation, and what should happen in the mean time with the tests?justinpatrin Sat Aug 19 22:15:26 2006 UTCModified files: /pear/MDB2/tests MDB2_usage_testcase.php Log:Remove incorrect test case for field case without portability