If its obscure, then I probably don't have it. The only SQLite manager I use is the CLI (rarely) and SQLite Expert by Coral Creek Software. The chances my software goes out into the wild would be probably slim to none anyways. :]
So the next best thing to setting the Application_ID to something and then validating it prior to opening the file would be to do the check against "SQLite format 3"+#0 realize it is an appropriate database, then read a table to get the application ID. On Sun, Jul 30, 2017 at 4:45 PM, Simon Slavin <[email protected]> wrote: > > > On 30 Jul 2017, at 9:34pm, Stephen Chrzanowski <[email protected]> > wrote: > > > Documented here: > > http://www.sqlite.org/src/artifact?ci=trunk&filename=magic.txt > > > > I have a routine that SPECIFICALLY looks for "SQLite format 3"+#0 to > > validate that the file in question is indeed a SQLite3 file hopefully > prior > > to actually opening any SQLite type of file handler on the actual file. > > > > If I wanted to, I COULD possibly set the application ID at DB creation > and > > add to my routine to validate that the application is opening the file I > > need it to? > > I’d recommend that you don’t do that. I’ve seen at least one SQLite > utility (called something like "Sqlite DB Manager" but not the well-known > one) which stomps on that value when copying or reconstructing the database. > > > Also, is 68 a HEX value or DEC value? > > Decimal. See section 1.2 of > > <https://sqlite.org/fileformat.html> > > Simon. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
