One process, two threads. I have found in documentation, that is not recommended to pass one connection from one thread to second one.
A partial succes, relative fast function, is proven with database file stored in ramdisk. Hard disk file storage 16 inserts per second. Ramdisk file storage 150 inserts per second. Temporary table in ram 1500 inserts per second. I have tried the one shared connection before i found the part in doc, that not recommends it, but there was some problems with locking in one configuration and segment violation in the second case. Jakub Ladman > Are you talking about two processes? If not, why these two threads have to > have separated connections? If it's not necessary, I'd opened disk db, > attach memory database to it (see http://www.sqlite.org/inmemorydb.html ) > and pass this db handle to both threads. One of them in this case will use > only memory part of the base (fast appending), another one will do > necessary selects and inserts to disk db part. After the db is closed, you > will only have disk part left. I don't know more about locking logic in > this case, because for performance reasons, it would be better for > example, if memory part only locked its part not affecting the disk part. > > Max > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
