[rt-users] Query Builder documentation

[Stephen Hancock]

OK - I can understand the need for parsing now for security sake but
the parenthesis () does not work for me. Additional parenthesis do
nothing in my case. Also even when the query is toggled correctly (In
Query Builder) , it appears that this is short lived. A return to
Advanced, A save, or a Search reformats the OR back to AND again and
we are back where we started.

Example:
In Advance: 
Owner = 'Nobody'  AND (  (  ( Status = 'new' ) OR ( Owner = 'Dale' 
AND Status != 'stalled' ) ) )

Click on applied and the Query Builder shows:

Owner = 'Nobody'
AND
   

       Status = 'new'
   AND
       Owner = 'Dale'
       AND Status != 'stalled'

Select the second AND and click on the And/Or toggle button and we
have (In Query Builder):

Owner = 'Nobody'
AND
   

       Status = 'new'
   OR
       Owner = 'Dale'
       AND Status != 'stalled'

Which is what we want and expect. However a return to Advanced or Save
or Search casues the OR to revert to AND again....

Adding additional () does not fix my problem. Am I doing something  wrong here? 


On Fri, 25 Feb 2005 00:20:02 -0500, Stephen Hancock
<sh.hancock at gmail.com> wrote:
> You are correct. My solution only works to one level of AND/OR.
> Apparently the Query Builder will not allow the two on the same level.
> 
> It will allow you to build a statement like:
> 
> que = 'gripe'
> AND
>     status = 'new'
>     OR status = 'open'
> 
> But not:
> que = 'gripe
> AND
>    status = ''
>    OR status = ''
> OR
>    whatever......
> 
> The operators change when moving from from Advanced to Query Builder
> and the toggle is inconsistent, sometimes changing all operators or
> all on one level instead of only the line selected.
> 
> This must be a bug - and a serious one since there does not seem to be
> a workaround with the advanced option. At least one that I can find.
> It would be better if the advanced just took straight SQL queries and
> did not reformat them for the query builder. It would be ugly but
> would probably work.
> 
> I think the question now seems to be is there a way to pass a SQL
> statement that will not be parsed to the db? and still be able to save
> the query?
> 
> 
> On Thu, 24 Feb 2005 13:26:14 -0500, Duncan Hutty <dhutty+rt at ece.cmu.edu> wrote:
> > On 01/31/2005 07:27 AM, Stephen Hancock wrote:
> > > Matthew,
> > >
> > > The QueryBuilder  doesn't like to mix AND and OR. I have had to get
> > > several statements up with the QueryBuilder and then go to the
> > > Advanced Menu to finish the statement. The Advanced menu will accept
> > > mixed statements just fine. I would suggest saving some  typical
> > > queries as templates and then allow users to load them and plug in the
> > > valuses they want.
> >
> > rt-3.4.1
> > While preparing queries, I have seen the problems with the query builder
> > not mixing AND and OR operators. Therefore attempting to follow the
> > above advice, I went to 'Advanced' and modified by hand.
> > I changed this:
> > ( Queue = 'gripe'  AND Status = 'new' ) AND ( Owner = '32'  AND Status =
> > 'open' )
> >
> > to this:
> > ( Queue = 'gripe'  AND Status = 'new' ) OR ( Owner = '32'  AND Status =
> > 'open' )
> >
> > Then I clicked apply. RT then returned me to the query builder page and
> > the query is changed back to the original.
> >
> > Suggestions?
> >
> > --
> > Duncan Hutty
> > System Administrator
> > Electrical and Computer Engineering
> > Carnegie Mellon University
> > _______________________________________________
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> >
> > RT Administrator and Developer training is coming to your town soon! (Boston, San Francisco, Austin, Sydney) Contact training at bestpractical.com for details.
> >
> > Be sure to check out the RT Wiki at http://wiki.bestpractical.com
> >
> >
>