Hello, On of the things that is supported by "big" databases is non-durable transactions that make the database updates much faster.
For example PostgreSQL has an option synchonous_commits and MySQLhas an option innodb_flush_log_at_trx_commit Basically I want to do many inserts and reads using the database and I want to keep ACI of ACID part. I mean I don't care that some of the transactions are get lost, but I do care that the database state would remain consistent in case of catastrophic fault. The simplest solution is to start a transaction and commit it once in a while it would make it **very fast** because fsync would be called only once in a while. The problem is that it works for one connection only and I can't do the same job from multiple connections and/or from multiple processes. Is there any way to solve this problem, any custom VFS or module? I understand that such option requires probably an additional thread or process to do this. Thanks a lot. Artyom Beilis -------------- CppCMS - C++ Web Framework: http://cppcms.sf.net/ CppDB - C++ SQL Connectivity: http://cppcms.sf.net/sql/cppdb/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
