> Because catching and dealing with the duplication is handled within > the library function, using these things appropriately should mean > that you don't have to do any fancy worrying about threads, processes > or simultaneity at all: if anything funny goes on, only one of the > INSERT operations will succeed.
Thank you for the info! Unfortunately things are a bit more complex, so I can't rely on the INSERT to tell me whether the file is there or not, because there's some heavy processing before that INSERT which of course shouldn't be done if the file is already there. I'm changing the program's logic in handling this, because SQLite is not at fault nor can it solve this problem on its own. I'm basically going to do a quick INSERT, then start the heavy processing and then do an UPDATE. This will let me do SELECTs to check existence from other threads without locking things up. Dennis _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
