Call this the "bitfield release." Turns out that MySQL 5's BIT column is not only different than the one in MySQL 4, it's also nearly impossible to deal with using DBI unless you call bind_param() and pass an explicit SQL type constant. Anyway, long story short, bitfields were bludgeoned into submission using a variety of techniques.
While I was in there, I had to fix the loader, which MySQL 5 also broke. And finally, some more SQLite ORDER BY bugs were causing tests to fail. All in all, not a fun release, but still recommended due to the bugs that it fixes. New version of Rose::DB required, files up on CPAN and SF.net, you know the drill. http://sourceforge.net/project/showfiles.php?group_id=147570 Rose::DB::Object: 0.64 (01.19.2006) - John Siracusa <[EMAIL PROTECTED]> * Worked around yet more SQLite ORDER BY bugs. * Improved the column trigger implementation. * Added support for MySQL 5's brain-dead new BIT column type. Classes must allow_inline_column_values(1) to use it due to the inability of DBD::mysql to bind BIT values correctly without explicit calls to DBI's bind_param() method. * Use alternate strategies for extracting foreign key information from MySQL 5 because the old way no longer works reliably. Rose::DB: 0.61 (01.19.2006) - John Siracusa <[EMAIL PROTECTED]> * Changes to support MySQL 5's brain-dead new BIT column type. * Changed SQLite's bitfield representation to use strings instead of integers to avoid numification that strips leading zeros. -John ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
