Attempting to convert a binary file to an sqlite3 database one challenge is performance. A first query returns 42,000 rows in less than a millisecond. Surprising as the query includes selecting rows then joining those with two other tables. I fetch/step through each row in about .33 milliseconds, .33 * 42,000 is about 19 seconds.

Attempting to convert a binary file to an sqlite3 database one challenge is performance. A first query returns 42,000 rows in less than a millisecond. Surprising as the query includes selecting rows then joining those with two other tables. I fetch/step through each row in about .33 milliseconds, .33 * 42,000 is about 19 seconds.

Attempting to convert a binary file to an sqlite3 database one challenge is performance. A first query returns 42,000 rows in less than a millisecond. Surprising as the query includes selecting rows then joining those with two other tables. I fetch/step through each row in about .33 milliseconds, .33 * 42,000 is about 19 seconds.

Attempting to convert a binary file to an sqlite3 database one challenge is performance. A first query returns 42,000 rows in less than a millisecond. Surprising as the query includes selecting rows then joining those with two other tables. I fetch/step through each row in about .33 milliseconds, .33 * 42,000 is about 19 seconds.

Attempting to convert a binary file to an sqlite3 database one challenge is performance. A first query returns 42,000 rows in less than a millisecond. Surprising as the query includes selecting rows then joining those with two other tables. I fetch/step through each row in about .33 milliseconds, .33 * 42,000 is about 19 seconds.

Attempting to convert a binary file to an sqlite3 database one challenge is performance. A first query returns 42,000 rows in less than a millisecond. Surprising as the query includes selecting rows then joining those with two other tables. I fetch/step through each row in about .33 milliseconds, .33 * 42,000 is about 19 seconds.

Attempting to convert a binary file to an sqlite3 database one challenge is performance. A first query returns 42,000 rows in less than a millisecond. Surprising as the query includes selecting rows then joining those with two other tables. I fetch/step through each row in about .33 milliseconds, .33 * 42,000 is about 19 seconds.

Attempting to convert a binary file to an sqlite3 database one challenge is performance. A first query returns 42,000 rows in less than a millisecond. Surprising as the query includes selecting rows then joining those with two other tables. I fetch/step through each row in about .33 milliseconds, .33 * 42,000 is about 19 seconds.

I linked sqlite to Visual Studio, but when I use the API of sqlite, it tells me -> Error LNK2001 “API”

I am attempting to run a sequence of sqlite3 prepared statements (some SELECT, some INSERT) and I want to be able to wrap them in a transaction, so if errors elsewhere in the code materialise, I can ROLLBACK the statement. However, it seems the sqlite3_step() functions automatically commit the results to the database: