On 7/23/07, Brian Kerr [EMAIL PROTECTED] wrote:
On 7/23/07, Ruslan Zakirov [EMAIL PROTECTED] wrote:
Do I understand right that the query is like Requestor.EmailAddress =
'xxx' OR Status = 'new' OR Status = 'open'?
* Note all binary operators (aggregators) are ORs.
The above queries were
Your problem may have something to do with the following statement issued
in the 3.6.4 release notes:
Use 'Watcher = X' inestead of 'Requestor = X OR Cc = X OR AdminCc = X' in
the SelfService interface. Both queries do quite the same job, but the
former is significantly faster.
I ran into query
On 7/23/07, James Moseley [EMAIL PROTECTED] wrote:
Your problem may have something to do with the following statement issued
in the 3.6.4 release notes:
Use 'Watcher = X' inestead of 'Requestor = X OR Cc = X OR AdminCc = X' in
the SelfService interface. Both queries do quite the same job, but
Do I understand right that the query is like Requestor.EmailAddress =
'xxx' OR Status = 'new' OR Status = 'open'?
* Note all binary operators (aggregators) are ORs.
On 7/23/07, Brian Kerr [EMAIL PROTECTED] wrote:
Hi,
This ticket system has been upgraded from 2.0.12 - 3.4.5 - 3.6.4.
Mysql
I believe that's what Brian was saying.
(from a follow-up email from [EMAIL PROTECTED]):
Requestor.EmailAddress LIKE 'tom' OR Owner = 'tom'
Forming this query in the query builder will create the nasty SQL. It
renders the RT instance unusable and all subsequent queries stack up.
Ruslan, is it
Brian Kerr wrote:
On 7/23/07, Ruslan Zakirov [EMAIL PROTECTED] wrote:
Do I understand right that the query is like Requestor.EmailAddress =
'xxx' OR Status = 'new' OR Status = 'open'?
* Note all binary operators (aggregators) are ORs.
The above queries were done with status delimiters.
The
