Along with the other replies already mentioned I'll pipe in with a reminder that any large blob fields should be the final field in a table's definition. Due to how the data is stored, to get the data for any particular field, SQLite has to go through/decode the data for all previous fields in a record.
So if you have a layout of... id integer primary key, big_blob_field blob, some_field_you_want text ... then if you "select some_field_you_want from table;" and a record has a 1GB blob in big_blob_field, then it'll have to go through 1GB of linked list overflow pages to get the value for some_field_you_want. (Some optimizations may apply) So be sure to define it as id integer primary key, little_field_1 text, little_field_2 int, little_field_3 float, big_blob_at_the_end blob -----Original Message----- From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> On Behalf Of Andy Sent: Tuesday, January 7, 2020 5:30 AM To: sqlite-users@mailinglists.sqlite.org Subject: [sqlite] Size limits What are reasonable limits for size Sqlite3 database file and large blobs? _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
