Are you sure you havent fallen victim to the MDB camps FUD
campaign?
Did you read his later message? he found the bug already reported 18 months ago complete with proposed patch, verified status and S2 (serious) severity ... and yet not fixed...
OP you might be better off filing a bug against either MySQL and F18 in bugzilla.redhat.com and let the maintainers decide what to do about it there ... if if you can test against community-mysql in F19 verify it there and again file in bugzilla.redhat.com ... at least there's some chance then of a Fedora patch being applied even if it's not fixed upstream after all this time ...
With the pending migration to MariaDB it might be worth double checking if the bug exists there and filing a bug with them - at least there's a reasonable chance of it getting fixed within a timespan less than 2 years that way ;)
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
