MySQL OFFSET require LIMIT.
So fixed it to use the biggest limit possible as it recommended in http://dev.mysql.com/doc/refman/5.0/en/select.html#id4651990
thank you for positing this Pull Request. I have automatically opened an issue on our Jira Bug Tracker for you with the details of this Pull-Request. See the Link:
@Everus what's the failing test case for this one?
This is wrong. It does not add the offset anymore when the limit is not null
I can't see what wrong in it, maybe you can point me in right direction.
However, as this fix is only for MySQL, I think it should be done in the MySQLPlatform only
Updated doModifyLimitQuery in SQLServerPlatform to handle subqueries …
Updated regular expressions in doModifyLimitQuery
Set guid type to require SQL comment hint
Type hinting for guid type now depends on platform's native guid support
Fixed wrong class names in SQLAzureFederationsSynchronizer
Merge branch 'master' of https://github.com/doctrine/dbal
Fix OFFSET without LIMIT cause MySQL syntax error.
Fixed in 3f220a1