Hi guys!
In #5874, Ocramius mentioned that the auto-escaping of column names for reserved keywords couldn't happen for Doctrine 2, but it could happen in Doctrine 3. I couldn't find any issue in the Doctrine 3 milestone, so I wanted to make sure the idea didn't get lost: I just saw a beginner hit this and get confused today (so 3.0 is our chance).
Is this still a "go" (i.e. yes, something we at least can do, assuming someone does the work) for Doctrine 3?
Thanks!
weaverryan
All 3 comments
Yeah, I think this should happen for 3.x.
We will have bugs with people doing mixed windows/mac/linux deployments, but less problems with reserved keywords used in mappings, and we can also get rid of the awkward "quoting in mappings" syntax.
Ocramius
on 23 Jan 2018
This already happened in master
ostrolucky
on 7 Aug 2018
This has been implemented in 08e2f779e3881f97c8136129fe9f951a9de2cb0d (and following commits) and the issue should closed.
PowerKiKi
on 8 Jun 2019
Related issues
doctrinebot
路
4Comments
neomerx
路
4Comments
kcassam
路
3Comments
goatfryed
路
3Comments
doctrinebot
路
4Comments
Most helpful comment
Yeah, I think this should happen for 3.x.
We will have bugs with people doing mixed windows/mac/linux deployments, but less problems with reserved keywords used in mappings, and we can also get rid of the awkward "quoting in mappings" syntax.