Hi. I'd definitely vote in favor of #2.
On Wed, Aug 18, 2010 at 7:32 AM, Andrew Hutchings <[email protected]>wrote: > Hi Patrick, > > OK, in branch lp:~thelinuxjedi/drizzle/drizzle-bug-617576 I have made the > coercibility function a plugin which is not built (or enabled) by default. > I have also created a basic coercibility test case with an include which > checks to see if the coercibility function is enabled. > > (could you tell I was bored when I got up this morning? ;) > > So, with the other test cases that use the function do I: > > 1. add the have_coercibility_function to the other tests that use it > 2. move the coercibility tests to my new test case > 3. something else? > > I think 2 would be best personally. > -- > Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/ > Certified MySQL Developer, DBA & Cluster DBA > Zend PHP5 Certified Engineer >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
