Quote create update and delete methods#552
Conversation
Add quote for fields name.
|
Hello, thank you for creating this pull request. However did not open it on the "master" Please open the pull request again for the "master" branch and close Nevertheless I have opened a Jira ticket for this Pull Request to track this http://www.doctrine-project.org/jira/browse/DBAL-847 We use Jira to track the state of pull requests and the versions they got |
|
We can't escape identifiers in this location because it would be a major BC break (any consumers that do escaping on their side would be affected). |
|
How about make it with addition parameter and disabled by default? Without escape DBAL make not to much sense. |
|
@mmuruev context-based switches are a pain - if you are using the DBAL with this setting on and the ORM with a quoting strategy then it is going to crash badly. This needs to be re-designed, but can't be done in 2.x |
|
Obvious it contain less pain then do custom crunches for any field values inside client code. Also how it will affect ORM if it will have no idea about this option and will do it in old fashion way. |
Not really - it is trivial to write a small wrapper that does this for you |
|
Of course not you just have to remember use it everywhere. Also if make |
|
Yeah, we can't clutter the connection with more parameters without breaking subclasses/wrappers. |
|
I can see that only class MasterSlaveConnection use Connection. And Just checked, additional parameter bring no harm because is have default value. Well what about use addition parameter in constructor? It receive array $params if add 'quoted' => bool pair it can be the solution. |
That's true only if you look at DBAL, and not at consumer libraries. The |
|
But that about __construct(array('quoted' = true), ...); It will harm no body. All interfaces will be in the same condition. |
Add quote for field names.