Eliminate SqlWalker deprecation trigger in Doctrine 3.3.0

[janedbal]

Resolves #50

[hellomedia]

Your solution did not work in my symfony project.

Using $this->walkSelectStatement($AST) generates the LIMIT 2 times for me.

The deprecation message is not clear about this, but reading the migration path below, I think that instead of extending SqlWalker, they want users to now extend SqlOutputWalker which includes the proper getFinalizer().

BC/migration path
The solution is to have a new subclass SqlOutputWalker. By moving to and extending this new class, users indicate that they are aware of the necessary changes and have removed the limit/offset parts from their own SQL generation. Of course, users would be free to return their own SqlFinalizer implementations in case they need special offset/limit handling code.

[janedbal]

@hellomedia Thank you, should be fixed in 2.0.2.

---

Note: issues are better for bug reports.