> On 6/07/2016, at 8:55 AM, Ward WIllats <sqlite-us...@wardco.com> wrote: > >> I have noticed that when I set max_page_count programatically to 16384 and >> read it back with the shell I get 1073741823. >> If I set max_page_count with the shell to 16384 and read it back >> programmatically, the program gets back 1073741823. >> Both the program and the shell can round-trip their own set/get cycle OK. >> > > Oh wait, you're going to tell me the value is transient to the connection, > aren't you? And 1073741823 is some kind of max sentinel?
Looks like it. Testing with an empty database created from scratch: $ sqlite3 test.db SQLite version 3.8.10.2 2015-05-20 18:17:19 Enter ".help" for usage hints. sqlite> pragma max_page_count; 1073741823 sqlite> pragma max_page_count=16384; 16384 sqlite> .quit $ sqlite3 test.db SQLite version 3.8.10.2 2015-05-20 18:17:19 Enter ".help" for usage hints. sqlite> pragma max_page_count; 1073741823 sqlite> pragma max_page_count=16384; 16384 sqlite> vacuum; sqlite> pragma max_page_count; 16384 sqlite> .quit $ sqlite3 test.db SQLite version 3.8.10.2 2015-05-20 18:17:19 Enter ".help" for usage hints. sqlite> pragma max_page_count; 1073741823 Same results with SQLite 3.13.0. Vacuum didn't help. Incidentally, 1073741823 is 2^30-1 (0x3FFFFFFF). This isn’t an endian issue either, as those bytes look nothing like 16384=0x4000. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
