1
1
- add columns() to row that returns a boost::tuple of various types so multple columns can be fetched at once
2
2
- look in to using BOOST_PP_ITERATE macro
3
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
- move _null_t, _exec_t and _set_index_t to sqlite::detail. Only the named instantiations of these structs need be in the sqlite namespace.
8
- add immediate_transaction
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.
9
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
10
9
- calling query.reset() before the commit fixes the issue
11
- need to check it's not fixed in latest sqlite
12
- will need to keep a list of querys that need resetting in the database :o(
10
- will need to keep a list of querys that need resetting in the database :o(
13
11
- turn on extended errcodes in open() and handle them in sqlite_error
14
12
- use sqlite3_db_mutex() to provide extended error information during sqlite_error construction - see sqlite::query::step() for example
15
13
- expand sqlite_error - perhaps use boost::system_error (see boost/asio/error.hpp for an example of extending system_error)
added
removed
TODO
