Jira issue originally created by user brandon.parise:
I made the following assumptions with the patch...
Should I assume differently? Or are there more assumptions I should consider?
Comment created by @beberlei:
My assumptions are phpMyAdmin biased. All statements are separated by ; - Lines dont matter. Problem here is that ; is a valid sign inside a literal.
Comment created by @guilhermeblanco:
We should not be so granular during this execution.
Also, OPTIMIZE, EXPLAIN, SHOW actually returns ResultSets and break the executeUpdate.
The correct way to do it would be using a RowSet support of PDOStatement.
The patch is ok, but a small modification and it'll be great to be merged. I'm assigning this issue to me and marking it as work in progress. I'll try to commit it tonight.
First draft for patch: http://pastie.org/809510
Problem is "nextRowset()" is not a method on the Doctrine\DBAL\Driver\Statement interface
In r7306 this issue was fixed.
Issue was closed with resolution "Fixed"
Imported 1 attachments from Jira into https://gist.github.com/58375ca36e51bcecb47d