Tntdb

Tntdb is a c++-class-library for easy access to databases. The interface is database-independent. Driverclasses are loaded dynamically.

The goal of it is to have easy access to databases. You don't have to worry about resourceleakage, because all objects you use directly are allocated on the stack and deleted automatically, when going out of scope. The interfaceobjects are wrappers to referencecounted instances, so you can copy them around at your own will. Resources are freed, when the last object goes out of scope.

Errorhandling is done exclusively with exceptionhandling. Just wrap your code with a single try-catch and you have full errorhandling. Exceptions are all derived from std::exception.

STL is used where possible and also STL-like and -compatible interfaces are offered, where suitable.

Tntdb is targeted for applicationprogramming. It is not suitable for generic databasetools. It does not offer e.g. schemaquery. You have to know, how your tables look like. Thats true for normal applications.

You use SQL for databaseaccess. No wrapperclasses like active resultsets or databound controls are offered. Instead you have best control over the database. You can use every SQL-trick you know to get most out of your database. Also this is a thin wrapper, so that you should have no big performancepenalty compared to direct access to the C-API.

The project started already some years ago as a postgresql-wrapper. Later I added a sqlite-3-wrapper.

The current status is, that there is a working mysql- and postgresql-driver-class. The sqlite-3-wrapper is included here, but it is just a early design-study. Tntdb works, but it is not dynamically loaded like the other drivers.

The public headers include documentation, which can be generated using Doxygen.

Also there are some small examples in the demo-directory.

What is new in this release:

• Major optimization of oracle driver:
• The oracle driver got a major optimization. When reading multiple rows, previously each row was requested separately from OCI. Now multiple rows are fetched in a single OCI call and passed row by row to the application.
• Add support for cxxtools::String (unicode string class):
• Cxxtools has a string class, which supports unicode. Tntdb now has full support for it. Unicode strings can be read and written transparently.
• Bugfixes and optimizations:
• Some minor bugfixes and optimizations are done in tntdb.

What is new in version 1.1:

• After more than 2 years new without stable releases it is time for updates. Cxxtools has hot huge improvements and feature enhancements like xmlrpc, a signal slot framework, anynchronous I/O and others.
• This implied some API changes. Still most of the existing code should run. Tntnet and tntdb needed some changes for this, so that the new tntnet and tntdb releases need cxxtools 2.0.
• Tntnet has got many small feature and performance enhancements. Luckily there was no much need for API changes. Almost applications should run out of the box by recompiling.
• Tntdb got some feature enhancements. Most important are maybe the support for auto incremented values using the method tntdb::Connection::lastInsertId(std::string) and support for user defined types by overloading 2 operators.

What is new in version 1.0.99:

• Tntdb has got some minor bug fixes and are adjusted to the API changes in cxxtools (which are quite small).

Requirements:

• cxxtools