On 1 Aug 2019, at 11:32pm, Randall Smith <rsm...@qti.qualcomm.com> wrote:
> Can an ATTACH request encounter a "locked database" error, or do these only > occur when an actual modification is attempted? How are ATTACHments > different from connections? Sorry, hit 'send' too soon. I don't think ATTACH can get a 'locked' or 'busy' error. I think you're right that those errors could happen only inside a transaction. A connection is the way SQLite keeps track of a database, the state that database is in, any transaction it is in the middle of, any statements it is in the middle of, the parts of the database which are cached, and lots of other things like that. Two different programs, or two different processes in one program, would be expected to use two different connections to talk to a database, or to two different databases. Otherwise one program or process might interfere with the other, and they would both have to have complicated logic in to figure out what to do about interference. On the other hand, the ATTACH command is a way for one connection to talk to two or more databases at once. Your request is a good example of why you might want to do this. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
