Closed beuss closed 1 year ago
Thanks for your contribution, are you able to share a small table dump and a list of options for mysqldump-php that would lead to this bug? I would like to add it to the test cases.
El lun., 30 nov. 2020 10:54, Sébastien Le Ray notifications@github.com escribió:
When hex-blob was specified and virtual columns of type blob or bit existed, produced dump file was invalid.
Move the "virtual-column" case on the top of the getColumnStmt process to totally ignore generated columns & switch to complete insert even if hex-blob is specified and we've a bit generated column.
You can view, comment on, or merge this pull request online at:
https://github.com/ifsnop/mysqldump-php/pull/214 Commit Summary
- virtual cols: fix unwanted insert on bit+hex-blob
File Changes
- M src/Ifsnop/Mysqldump/Mysqldump.php https://github.com/ifsnop/mysqldump-php/pull/214/files#diff-2bdc9acc0b460325abf5e827d6c50a098f55c2d555a5aa5fb847f545b230d3e5 (8)
Patch Links:
- https://github.com/ifsnop/mysqldump-php/pull/214.patch
- https://github.com/ifsnop/mysqldump-php/pull/214.diff
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ifsnop/mysqldump-php/pull/214, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHMH2G65JQ7BFZTY7FEEHLSSNTV3ANCNFSM4UHKQ7SA .
Finally got some time to implement tests and a fix.
When hex-blob was specified and virtual columns of type blob or bit existed, produced dump file was invalid.
Move the "virtual-column" case on the top of the getColumnStmt process to totally ignore generated columns & switch to complete insert even if hex-blob is specified and we've a bit generated column.