F
Frank Meulblok
Guest
Just to avoid a common misconception: Database statement cache will *not* accurately report exactly what the client is doing. You get the details on the last database accessing statement that was executed only. No more, no less. So if for example you've got code that FILLs a prodataset and then does some processing on the dataset that pulls into an infinite loop for some reason, the Database statement cache will only point to the FILL operation since that's the last time the code accessed the database. Likewise, if the code uses multiple statements to read different tables - you get only one of them, not all of them. See also: knowledgebase.progress.com/.../P150383
Continue reading...
Continue reading...