1
- add columns() to row that returns a boost::tuple of various types so multple columns can be fetched at once
2
- look in to using BOOST_PP_ITERATE macro
3
- make basic_statement and database keep a shared pointer to the database handle so the classes can be made copyable. Also:
4
- the wrappers around the handle can clean them up after use
5
- the actual wrappers wround the handles can be made in sqlite::detail
6
- this will also make the implementation od rows (to get round the forced non-dependency of rows on querys) a little easier to swallow.
7
- committing a transaction during a query (i.e., when sqlite3_step() has returned SQLITE_ROW) causes an error. To counter this:
8
- need to check it's not fixed in latest sqlite; write test program
9
- calling query.reset() before the commit fixes the issue
10
- will need to keep a list of querys that need resetting in the database :o(
11
- turn on extended errcodes in open() and handle them in sqlite_error
12
- use sqlite3_db_mutex() to provide extended error information during sqlite_error construction - see sqlite::query::step() for example
1
- turn transaction in to basic_transaction and create transaction, exclusive_transaction and perhaps recursive_transaction?
13
2
- expand sqlite_error - perhaps use boost::system_error (see boost/asio/error.hpp for an example of extending system_error)
14
- see if we can #include "sqlite.h" in to a namespace.
16
we better encapsulate the library
17
we can reuse "sqlite3" as a namespace
19
makes access to real sqlite stuff awkward to sqlite3cc users, but does this matter? they can't access database._handle anyway!
20
potential incompatibility when linking to libraries that also link against sqlite
21
- fix step() inconsistency - query::step() returns a row, whereas basic_statement::step() and command::step() return an int return code
22
- query::prepare() isn't being called during construction (form
23
basic_statement's constructor)
3
- see if we can #include "sqlite.h" in to a namespace. Cons: no easy access to real sqlite stuff. Pros: can't access database::_Handle anyway, so Cons don't matter and we better encapsulate the library
added
removed
TODO
