Re: pilog question about combined indexes

2019-10-24 Thread C K Kashyap
Got it! Regards, Kashyap On Thu, Oct 24, 2019 at 7:46 AM Alexander Burger wrote: > On Thu, Oct 24, 2019 at 07:16:31AM -0700, C K Kashyap wrote: > > If I understand correctly - the filter clause is redundant because it > does > > not subset the records generated by the generator? > > Yes. In

Re: pilog question about combined indexes

2019-10-24 Thread Alexander Burger
On Thu, Oct 24, 2019 at 07:16:31AM -0700, C K Kashyap wrote: > If I understand correctly - the filter clause is redundant because it does > not subset the records generated by the generator? Yes. In this simple case, where we have only a single generator, this is correct. You don't need 'select'

Re: pilog question about combined indexes

2019-10-24 Thread C K Kashyap
Thanks Alex ... I think I am getting there :) - It's pretty neat the more I get into it! If I understand correctly - the filter clause is redundant because it does not subset the records generated by the generator? When I look at the filter used in app/gui.l I wonder if the filter (range @Nr @@

Re: pilog question about combined indexes

2019-10-24 Thread Alexander Burger
Hi Kashyap, > : (? (select (@Tel) ( (mob +CuSu "37 176 86303") ) )) > @Tel={C1} > ... > : (? (select (@Tel) ( (mob +CuSu "37 176 86303" tel +CuSu "37 176 86303") ) > )) > -> NIL > > The first query returned as expected. The second one I believe means - look > for "37 176 86303" either in tel

pilog question about combined indexes

2019-10-24 Thread C K Kashyap
Hi, I tried the following : (? (select (@Tel) ( (mob +CuSu "37 176 86303") ) )) @Tel={C1} -> NIL : (? (select (@Tel) ( (mob +CuSu "37 176 86303" tel +CuSu "37 176 86303") ) )) -> NIL The first query returned as expected. The second one I believe means - look for "37 176 86303" either in