Opening just one (Read/Write|Create) conection SQLite should never signal
busy to that connection after it successfuly acquired it.
Since you can use thight loops and it should be up to SQLite how long its
takes for the individual command execution and how many threads its opens up
to accomplish the job at hand,
it should come back sync. otherwise it will break the loop forcing to launch
a signal handling thread.
My task setup:
A table "ART"
A virtual fts5 contentless table:
CREATE VIRTUAL TABLE "OCR" using fts5 (content='',FullText)
CREATE TRIGGER "ART_AD" AFTER DELETE ON "ART" BEGIN INSERT INTO "OCR"
to keep the virtual table sync with row deletation of "ART"
0 Collecting user input from grid selection into a list of SQL DELETE range
statements (BETWEEN value1 AND value2;)
1 Open connection
3 the delete loop on the list.
SQLite breaks the loop with signal "busy" if one or more of the delete
ranges are bigger than ~20.000 rows.
Without the transaction frame seems to be ok.
Is my "assumption" above wrong and I allways have to take care of eventual
interraptions from SQLite?
Is this a limitation because of the trigger forces a separate thread for the
virtual table, which is maybe not that thightly integrated?
Is this a bug?