Query options??

[martinwcole]

Re: Query options??

yes - both with and without the options

t1=table.open("patients")
query.filter=""; query.order=""; query.options=""
query.filter="left(lastname,1)='a' .or. left(lastname,1)='w' .or. left(lastname,1)='s' "
query.order="lastname"
query.options="T"
dim shared uid as c
idx=t1.query_create()
msgbox("","" + idx.records_get())
t1.fetch_first()
while .not. t1.fetch_eof()
 uid=t1.Uniqueid
 temp=lookup("patients","uniqueid=" + quote(var->uid),"uniqueid")
 t1.fetch_next()
end while
msgbox("","" + query.filter)
t1.close()

[Tbaker]

Re: Query options??

Martin

Back in Post 10, I gave Glenn a test zip that was similar to your code.

Both the "T" option and the "X" option worked every time with the lookup on the same table (the only difference was that I only had 43 records in the table and in Glenn test he has over 5000 records of which 2244 will be in the loop.


In Glenn's app, something is causing the query to be dropped. It may have something to do with the lookup or it could have something to do with the number of queries that are in his test app.

I guess we will have to wait to see if Selwyn or someone replies to Glenn's Bug report.

FWIW

Tom Baker

[martinwcole]

Re: Query options??

ok - here's another iteration, with a double loop and a tracer
I tested it with query.options="X","T", and ""
ran successfully in all cases

'Date Created: 03-Jun-2010 08:00:36 PM
'Last Updated: 04-Jun-2010 01:41:39 PM
'Created By  : martin cole
'Updated By  : martin cole
'this is a dummy script meant to reproduce a 
'possible bug or issue where query slots are used by lookup() in recent patches, whereas they were not in early releases, and/or in V8
t1=table.open("patients")
recds1=t1.records_get()
temp="a"; temp2="a" + crlf()
for i=1 to 25
temp=increment_value(temp); temp2=temp2 + temp + crlf()
next
'get all 26 letters in a variable
dim shared qry as c
recds=0
n=w_count(temp2)
for i=1 to n 
 query.filter=""; query.order=""; query.options=""
 qry=word(temp2,i,crlf())
 query.filter="left(lastname,1)=" + quote(var->qry)
 query.order="lastname"
 query.options="T"
 dim shared uid as c
 idx=t1.query_create()
 recds=recds + idx.records_get()
' msgbox("","" + idx.records_get())
 t1.fetch_first()
 while .not. t1.fetch_eof()
  uid=t1.Uniqueid
  temp=lookup("patients","uniqueid=" + quote(var->uid),"uniqueid")
  if temp <> uid
   msgbox("","error temp not equal to uid")
  end if 
  t1.fetch_next()
 end while
 idx.drop()
next
msgbox("recds1= " + recds1,"recds= " + recds + "  " + query.filter)
t1.close()

ps - i have 1738 records in the patients table

[Tbaker]

Re: Query options??

Martin

There is a lot of activity in your latest code. And the result is the same, they work with the "T" option as well as the "X" and even with no option.

I have gone over Glenn's code and other than it is also busy with five queries prior to the the looping section, I can't find anything wrong with the syntax (Unless I missed something).

Again, something is diffrent in Glenn's code and I cannot put a finger on what it is that causes the query to drop and indeed it does drop.

So far a lot of good has come from this posting - there is a lot of valuable information in what was posted. Now all we need is a solution.

Tom Baker

[peterg000]

Re: Query options??

Sorry for the delay in posting an update .... family illness

Anyway .... what I got back from Selwyn was ...

"i am getting an error when i try to run your script, but we did make a change to lookup() so that it uses temporary queries"

I sent him back a reply letting him know if the error was with the operation, to ignore. And I also asked him if he ment the lookup() was changed to temp queries in V10 or he just changed it to temp queries in latest pre-patch?? .... didnt get an answer back ... not sure I will.

So .... if lookup() is using temp queries, it would make sense that the recursive lookups() in my code would eventually bump someone out of the available slots and if my main query uses query.options = "T", that makes it subject to getting bumped.

The thing im struggling with though, if I use options = "" things work ok and my main query survives the loop process. I would think it wouldnt matter and the same amount of slots are available and it would still eventually get bumped. My theory is, there are certain slots for temp queries and slots for standard queries ..... just a theory .... only person that can tell us is Selwyn .... I asked for some explanation .... no reply as of today.

Glenn

[peterg000]

Re: Query options??

Martin .... the test you ran on the patient DB and all options worked .... was that V10?

Glenn

[martinwcole]

Re: Query options??

yes - release cand 5 i think