Hello,
in my mfc application are 100-10,000 object properties (depending on app
setup) used by two threads. The properties are not threadsafe (most of
them are doubles or int). Upto now (15 years running code) there was no
problem. Only one thread writes to the properties.
Main thread accesses the properties every 5 msec. The second one
accesses on demand (every 50-2000 msec).
Now i have to add an http server interface to my application. The server
is running, but i'm not sure, if the last 15 years of not threadsafe
access will be okay any longer. So i think about to store the properties
in a sqlite memory database. The threads prepares their own
sqlite3_stmt's with select statements to the properties currently needed
- to have fast access to the database values.
My question: Is their any limitation of sqlite3_stmt bound to a
database? How much memory is used by a sqlite3_stmt?
Thx for any hint
heribert
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
