[rt-users] WHERE clause when using LimitXXX

[Rafael Corvalan]

Great. So then, are the following assumptions right:

1) Between two different fields (for example Status and Owner),
   the operator used by the SearchBuilder is "AND" and cannot
   be overriden.

2) For a specific field (for example Status), the operator
   used depends on the field type, but can be overriden
   using ENTRYAGGREGATOR 

? Thanks.

-----Original Message-----
From: Jesse [mailto:jesse at fsck.com] 
Sent: mercredi, 1. août 2001 08:15
To: Rafael Corvalan
Cc: rt-users at fsck.com
Subject: Re: [rt-users] WHERE clause when using LimitXXX





On Wed, Aug 01, 2001 at 08:11:12AM +0200, Rafael Corvalan wrote:
> Just because if they are owned by someone, it should not be "new". It 
> was just a personal opinion... But thinking more in depth, you're 
> probably right. I can "Take" a ticket because I know *I* will work on 
> it, but just "Open" it 1 hour later.
> 
> OK, I accept this idea. How can I know (I can do some tests, but I'd 
> prefer to have a logical way to know it) what will I obtain using:
> 
> $Tickets->LimitOwner(VALUE => $RT::Nobody->Id); 
> $Tickets->LimitStatus(VALUE => "resolved", OPERATOR => "<>"); 
> $Tickets->LimitStatus(VALUE => "dead", OPERATOR => "<>");
> 
> 
> because of course this doesn't work, since there is a logicl OR 
> between the "Status" where clauses, and not an "AND". In that case I 
> could inverse and tell Status="new" or "Status"="open" or.....


OR you could use ENTRYAGGREGATOR => 'OR' in the LimitStatus statements.
> 
> But am I sure that between the Owner limit and the status limit I am 
> using an AND clause?

yes. that's currently built into SearchBuilder.