Roadmap

This is a tentative roadmap or wish list with no specific dates attached yet shown below. For detailed roadmap discussion and agreed tasks assigned to future releases, refer to the Issues Milestones.

If you'd like to discuss anything listed below or anything new, you are welcome to do so and post to SOCI mailing lists.

Future

C++11 support
- #336 adds support for C++11 compilation mode
- Switch would mean SOCI would be no longer backward compatible with C++03 or previous versions.
New API for DDL operations to provide unified way to CREATE, DROP and ALTER database objects.
New backend for VoltDB
New backend for Microsoft SQL Server (native, not based on ODBC, see FreeTDS)
New backend for Sybase (see FreeTDS)
~~New backend for DB2.~~ (already in 3.2).
Neo4j + Cipher support?
NoSQL support?
- New backend for Apache CouchDB
Rename headers from .h to .hpp and replace - with _ in all file names.
Complete support for C++ integer types (see RFC1)
Create backend-specific namespaces and drop backend name prefix from names (i.e. odbc_soci_error would become odbc::soci_error)
Refactor public API to Non-Virtual Interface Idiom (NVI).
Add BOOLEAN data type support.
Add NUMERIC/DECIMAL data type support (prototype for soci::numeric in mloskot/postgresql, alternative is Boost.Multiprecision)

Version 4.0.0

v4.0.0 milestone
#332 Documentation in Markdown with Sphinx (or cldoc)
Add BINARY data transfer support
- Critical if we would like to support features like (geometry, raster or point cloud data types) and geometry data available in most DBMS.
Add Unit Tests with mocking
- Alex Ott's article on Test-driven development and unit testing with brief discussion with Alex on Boost.Test and Turtle (Boost-oriented library, might be proposed).
Style unification
- ClangFormat could make it easy.