Doctrine Bot

Comment created by osvi: "its hard to really keep track of all of the different reserved words for all RDBMS" That's the main point for me.

Comment created by kreischweide: @Damian thanks for the hint. I just ran into a similar situation. Not every project is a startup. I tried to use doctrine2 on a customers...

Comment created by rjmunro: What do you mean by "Quoting everything is like hitting all the SQL with a huge big hammer"? Is there a performance hit? I have always...

Comment created by @ocramius: If you want quoting by default on everything we have a quoting strategy (in ORM) that you can use. I don't think quoting everything by default...

Comment created by @deeky666: Hello, if I understand correctly, the issue of quoting reserved keywords automatically is solved in https://github.com/doctrine/dbal/pull/302. Besides reserved keywords you can still decide quoting or not...

Comment created by thinkscape: It's still broken in 2.4. PR 302 only selectively fixes indexes, PK and FK, but ALTER and all CRUD will still fail (and schema tool will...

Comment created by thinkscape: QuoteStrategies are not used for ALTER queries. This means that using the EagerQuoteStrategy mentioned above won't fix invalid ALTER queries generated by schema tool. For ALTER...

Comment created by @doctrinebot: A related Github Pull-Request [GH-379] was closed: https://github.com/doctrine/dbal/pull/379

Comment created by lavoiesl: My 2 cents from [DBAL-96](http://www.doctrine-project.org/jira/browse/DBAL-96): 1. Users should not have to worry about platform-specific quoting when using the query builder or helpers, the DBAL should do...

Comment created by thinkscape: Sebastien, ad 3. that is incorrect. Read the ticket more closely, look at the PR, look inside schema tool and platform classes. There is already a...