hi @janmeier - I wasn't aware of the MySQL issue. I feel that the limit hack for MySQL (when a limit is not specified) should be stuffed into the MySQL dialect generator. 

an alternative could be to require that limit and offset always be specified as a pair - this avoids having to implement the hack and means you'll never get that "Sequelize refuses to return trillionth+1 record when only specifying 'offset'" issue ;-).

other ORM/DBAL projects have the run into the same issues, e.g.:

> https://github.com/doctrine/dbal/pull/261/files

note that there they chose for your 'big number' hackin their  equivelent of the 'dialect' ... I am wondering whether the big number hack needs to take account of the size of 'MAX LONG' or should we opt to define the 'big number' as a string?

oh and do you need me to add a fix for this problem in this PR? :)