Doctrine Bot

Comment created by @deeky666: If those are reserved keywords, they should be added to the "PostgreSQLKeywords" class and they will be quoted by Doctrine. As far as I can see...

Comment created by dualmon: This is the closest existing issue I could find to a problem we are having with the schema tool update and case insensitivity. If this is...

Comment created by asentner: I am also having this issue. The down() method always adds: $this->addSql('CREATE SCHEMA public'); Same environment, also using Postgres. Any chance this is on anyone's radar...

Comment created by acasademont: Hit by this too. The problem seems to be that the "public" namespace is not added to the table names by default and hence the diff...

Comment created by @ocramius: I don't think those namings are really important. There's one major change to do, which is to somehow get rid of the staticness of the `Doctrine\DBAL\Types\Type`...

Comment created by till: I agree on the static. But I'd also like the API to be cleaned up and the remove method.

Comment created by @deeky666: API cleanup and staticness can be addressed in 3.0 for the first time. Otherwise we cannot keep BC. You can use Doctrine\DBAL\Types\Type::overrideType('someType', null); as a workaround...

- is duplicated by [DBAL-120: MySql platform getAlterTableSQL does not quote existing column names](http://www.doctrine-project.org/jira/browse/DBAL-120) - relates to [DBAL-45: Add CLI tool that checks for Reserved Keywords](http://www.doctrine-project.org/jira/browse/DBAL-45) - relates to [DBAL-477:...

Comment created by @deeky666: [~beberlei] this is an interesting approach and I like it. But I have some complaints about it. 1. I doubt users will be happy about forced...

Comment created by lavoiesl: My 2 cents: 1. Users should not have to worry about platform-specific quoting when using the query builder or helpers, the DBAL should do that for...