Thanks for quick help. So this is related to Thread-local
storage, which as I found it now, well documented, expected, and
works as designed.
On Monday, 2 March 2015 at 07:20:49 UTC, Vitalie Colosov wrote:
Now it all makes sense. Thank you.
Maybe it would make also some sense if I would have gotten some
kind of exception trying to access the variable which was not
populated by the running thread, instead of successfully
getting empt
On 3/2/2015 4:20 PM, Vitalie Colosov wrote:
Now it all makes sense. Thank you.
Maybe it would make also some sense if I would have gotten some kind of
exception trying to access the variable which was not populated by the
running thread, instead of successfully getting empty string... so this
wou
Now it all makes sense. Thank you.
Maybe it would make also some sense if I would have gotten some
kind of exception trying to access the variable which was not
populated by the running thread, instead of successfully getting
empty string... so this would be observed easily during the
testing,
On 03/01/2015 09:47 PM, Vitalie Colosov wrote:
> global variable
A module-scope variable is thread-local by-default. Every thread will
have a copy of that variable.
If you want to share data, you must define it as 'shared' (or __gshared).
> which was populated in main() function
In that cas
After some analysis, it looks like related to the code parts
which I have omitted "for simplicity", and in particular - I was
creating the query using global variable which was populated in
main() function. It appears that when I spawn the function, it
does not see the value of the global varia
Hi,
I am not able to query SQLite3 database files using threads;
without threads it is working fine.
I tried both etc.c.sqlite3 and d2sqlite3, and both seem to be
facing the same issue:
They stuck when executing a select query (using sqlite3_exec(...)
for etc.c.sqlite3 or using RowCache(db.exe
