Results 69 comments of Doctrine Bot

Comment created by thinkscape: Sebastien, ad 3. that is incorrect. [Read the ticket](http://www.doctrine-project.org/jira/browse/[DBAL-40]%28http://www.doctrine-project.org/jira/browse/DBAL-40%29?focusedCommentId=21169&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21169) more closely, look at the PR, look inside schema tool and platform classes. There is already a...

Comment created by ancpru: IMO the big problem is, that behaviour across the RDBMs may be completely different: Some preserve case and are case-insenstive if not quoted (the nicest approach)...

Comment created by bigfoot: I've mapped the field as nullable=false, so it should never be null. If you cannot merge this quickly, you should at least add an warning in...

Comment created by @ocramius: Can you add a few usage examples? What APIs are affected?

Comment created by Vicente69: Sorry, I don't understand what kind of information you're missing. The API is the _Doctrine\ORM\Query\Expr_ class, in the ORM. The need is to improve the _like_...

Comment created by @ocramius: [~Vicente69] this is exactly what the kind of feedback I was asking for. As of http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/dql-doctrine-query-language.html#ebnf, the `ESCAPE char` is actually supported: `LikeExpression ::= StringExpression ["NOT"]...

Comment created by Vicente69: Sure, that's it :), using direct DQL for requests, it is possible to write such conditions. However, as you notice it, using the _QueryBuilder_ and the...

- is referenced by [DDC-3681: [GH-1378] Feature to force-increment entity version](http://www.doctrine-project.org/jira/browse/DDC-3681) - is referenced by [DDC-3823: [GH-1456] No-frills support for Entity version bumping](http://www.doctrine-project.org/jira/browse/DDC-3823)

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

Comment created by dhager: First, I'd like to toss another scenario on the pile: Consider an entity like, uhm, FavoritePurchaseOrders. It refers to an owning User, references a set of...