On Tue, Oct 2, 2012 at 8:42 AM, Staffan Tylen <staffan.ty...@gmail.com> wrote:
> Mark, thanks for the description of the trace function etc. I've played a > bit with it and it seems to work but not always. Have a look at the example > below: the first call to self~getdata correctly results in a trace message > but the second call to the same method, triggered by an expand action, does > NOT work and generates message Error 91.999: Message "EXEC" did not return > a result > I can't see what's wrong with this. Comment out the db~trace(.sqltrace~new) > statement and the problem is gone. Any ideas? Yes, I see what the problem is. It is not your code, but rather a problem with the ooSQLite callback code. Your test brought out the problem because the second exec() is executing on a different thread then the traceHook was initially installed on. The first self~getdata works because the exec() executes on the same thread as the traceHook was installed on. I can fix this, give me about a day to put a new build up on SourceForge. By the way, providing a simple example that demonstrates the problem is *extremely* helpful. Thanks. -- Mark Miesfeld ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
