The goal of the Database Template Library is to make ODBC recordsets look just like an STL container. As a user, you can move through containers using standard STL iterators, and if you insert(), erase(), or replace() records in the containers, changes can be automatically committed to the database for you. The library's compliance with the STL iterator and container standards means you can plug the abstractions into a wide variety of STL algorithms for data storage, searching, and manipulation. In addition, the C++ reflection mechanism used by the library to bind to database tables allows generic indexing and lookup properties to be added to the containers with no special code required from the enduser. Because the code takes full advantage of the template mechanism, the library adds minimal overhead compared with using raw ODBC calls to access a database.
DBPrism is an open source framework to generate dynamic XML from a database. It connects Oracle databases with Apache Cocoon, providing a high performance DBGenerator with functionality such as parallel content aggregation and ESI cache protocol. It also includes a powerlful database oriented CMS built on top of Apache Cocoon2 and DBPrism.
db4o is an object database for Java and all .NET environments. Its features include ACID transactions, automatic class schema recognition, query-by-example, a S.O.D.A. object querying API, native queries, LINQ support on .NET, callback methods, memory files, cascade-on-delete, multi-threaded access, and Java Webstart and servlet support.
MUSCLE (Multi User Server Client Linking Environment) is an N-way messaging server and networking API. It includes client-side networking APIs for various languages, including C, C++, C#, Delphi, Java, and Python. MUSCLE lets programs communicate over a network via streams of serialized Message objects. The included server program ("muscled") lets its clients message each other and store information in its server-side hierarchical database. The database supports flexible queries via hierarchical wildcarding, and "live" updates via a subscription mechanism.
mxODBC is an extension package that provides a Python Database API compliant interface to ODBC 3.5 capable database drivers and managers. In addition to the capabilities provided through the standard API it also provides a rich set of catalog methods that allow you to scan the database for tables, procedures, etc. Furthermore, it uses the mxDateTime package for date/time value interfacing eliminating most of the problems these types normally introduce (other in/output formats are available too). Supported database targets are MySQL, Solid, Sybase, Oracle, Infomix, Adabas, MS Access, MS SQL Server and many other databases with ODBC drivers. Also supported are the Windows ODBC manager and the Unix ODBC managers iODBC and unixODBC, as well as the EasySoft ODBC-ODBC bridge.
Net::Z3950::SimpleServer is a Perl module which implements the server side of the Z39.50 (information retrieval) protocol. It hides the complexity of network exchanges, packet serialization, and session handling. You are required only to implement simple callbacks to support searching and record retrieval. It is the basis of the "Zoogle" project, which is a Z39.50 gateway to the Google web index.
The Easysoft ODBC-ODBC Bridge allows applications on one machine to access ODBC data sources on another. It supports multiple concurrent connections from multiple clients to multiple target databases. The principle application is to enable access from Linux and Unix platforms to remote ODBC databases. For example, Apache/PHP programs on Linux can read/write data held on MS SQL Server on Windows, and Perl programs can read/write data held in a MS Access database. Supported applications include Applixware, Open Office, Python, Rexx/SQL, mnGoSearch, OpenLDAP, and Oracle sqlplus. Supported platforms include Linux, MacOSX, IBM zSeries, Windows and various Unix flavors.
Redland is a set of C libraries providing a high-level API for the Resource Description Framework (RDF), allowing it to be stored, parsed, serialized, queried, and manipulated. It has an object-based, modular design and comes with detailed reference documentation and examples. Redland supports all RDF vocabularies such as FOAF, RSS 1.0, Dublin Core, DOAP, and OWL, the query languages SPARQL and RDQL, and all RDF syntaxes including Turtle, RDF/XML, RDF/JSON, RSS, Atom, RDFa, and GRDDL.