hm, it seems this method only appears in the trunk unit tests, so it is probably not anywhere else. It doesn't exist in 0.11.

The current structure does not support OR/AND changes.

I refactored this part in trunk (2.0) to support OR/AND inclusions, but it cannot be backported (since it doesn't have _dqlParts array in 2.0).

Maybe in a deep change I can try to adapt it to work in 1.0, but I cannot be 100% it'll be possible.

Actually what's done internally? $q->addWhere($where) does: $this->_dqlPartswhere?[] = $where;

And later when $q->getDqlQuery() is called: $where = implode(' AND ', $this->_dqlPartswhere?);

I already spoke with jonwage about this change, but we both agreed that change the DQL parser now may lead to unexpected situations. I'm forwarding this ticket to 1.1, maybe I can refactor Doctrine_Query in a later stage and update source.

Cheers,

We will have to hack this functionality in to Doctrine 1.0. It is already correctly implemented in trunk but due to some deeper problems we can't implement it as cleanly as is done in trunk. Attached is something I put together to add the following methods:

andWhere()
andWhereIn()
andWhereNotIn()
orWhere()
orWhereIn()
orWhereNotIn()

The and method are essentially just proxy methods as they already exist, but to match the or api I created the proxies.

Note: The attached patch still has many problems that need to be talked about and worked on.

We are changing the priority of items to address the most important ones for RC1.

(In [4848]) fixes #1331. Added andWhere, andWhereIn, andWhereNotIn, orWhere, orWhereIn, orWhereNotIn support to 1.0. Added some coverage to this support.