D. Richard Hipp wrote:
Most people who are using SQLite successfully have, I imagine,
either written their own wrappers around the core API (which
is not hard as I do provide you with a lot of helper routines
such as sqlite3_vmprintf and friends) or they are using an existing
wrapper written by someone else.
Indeed I wrote a thin wrapper when I started using SQLite 6 months ago.
I now retract my request for more control over the open function, as one
of the features of SQLite that I really liked was that it didn't have an
extensive set of "features". I can and will implement the read/only and
exclusive tests in my own open wrapper, and return or throw where
appropriate.
