On 1/23/2014 5:12 PM, Joseph L. Casale wrote:
The bulk load doesn't have to be done this way, only one process loads data and even a single connection can be used but that would segment the wrapper.
SQLite transaction is a property of a database connection - there ain't no such thing as a transaction spanning multiple connections. So, if you want to utilize SQLite transactions as you atomicity mechanism, then all changes will have to be made on a single connection. If for whatever reason you want to make changes atomically on multiple connections, then you face an unenviable task of designing your own atomicity mechanism - I don't believe SQLite provides anything to help you with this, and in fact will fight against you (only one connection can write to a given database file at any given time). Choose your poison.
-- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
