On Wed, Dec 15, 2010 at 11:14 PM, Doug <pa...@poweradmin.com> wrote: > . And getting concurrency with processes means you introduce the > complexities of interprocess communication/synchronization which is much > easier to handle with threads in the same process. > > Doug, nothing stops you from using different threads of different connections in the same process. That's how for example my fts implementations works. When the user presses keys in the edit box, the secondary thread look-ups word that starts with those letters in a different connection to the same base, works like a charm. Sure, memory usage can increase in this case, but if one compares footprints of modern libraries, frameworks and so on with sqlite, even with several connections sqlite is still the winner
Max Vlasov _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
