Wrap enough functionality in the statement class to allow the user to execute statements and retrieve results.

This explicitly doesn't try to deal with the inherent non-threadsafety
of the sqlite statement type.  That will only come up if you're trying
to reuse statements, presumably for performance, and once we're doing
that, the code that mediates reuse should ensure that only one client
has its hands on a given statement at once.  (even non-threaded reuse
is dangerous!)

0 files changed, 0 insertions, 0 deletions