-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/04/2010 09:41 PM, Aron Rubin wrote: > Most execution environments that support calling including C and > Sqlite use a stack of frames.
C has a conceptual stack - the actual implementation does not require one. SQLite has no such thing - the interface is the SQL language. > Looking at the Sqlite code, VDBE maintains a stack of frames. VDBE is an implementation detail and it doesn't require using frames. > I am suggesting that these frames are > assigned an id that is unique for that parallel execution. I don't get the link between frames and parallel execution. Frames give you the depth of recursion. All threaded environments give you a unique id per thread eg pthread_self or GetCurrentThreadId. Also note that there is no parallel execution - a mutex is held on each connection while vdbe is executing. > If each parallel path, i.e. > database open from programs, is assigned a unique id then the > combination of that id and the call depth would be sufficient for my > purposes. You've avoided actually saying what problem you are trying to solve (just a potential solution). In any event you can add a user defined function that gets the current real (processor level) stack pointer. It will be thread and vdbe unique. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvhE68ACgkQmOOfHg372QSQigCfUQTeQEM3AfDotJoebzCj4UBg SEEAn1bN2ygr43q8pdUmVwD9XuwluNu5 =N+54 -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
