hi, Is it possible to add some informations about locking mechanism in the wiki page VirtualTables?
I'm facing concurrency problem in developing a cluster Sqlite database. One table per database. Multiple databases indexed like x.db, x.db-001, x.db-002, x.db-003, ... each containing a choosen number of rows (like 100K rows with incremental prikey). Conceptually, this should increase concurrent access to data... 1) "CREATE VIRTUAL TABLE" applied on the x.db 2) Update a row in x.db-001 via x.db vtab 3) Update a row in x.db-002 via x.db vtab I'm afraid each update processed on the x.db to modify x.db-001 via the virtual table module could create a lock on x.db and x.db-001. So the trick will be useless. I was thinking integrating some other storage engine like PostgreSQL or MySQL with virtual tables... but the locking concurrency problem could be the same. Any ideas? Thanks. -- Guillaume ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
