DBConnect (Database Connect) API is an easy to use C++ object API to allow applications to connect to databases. Your DB applications can now become cross platform and cross databased.
The API currently implements MySQL, Oracle8 and PostGreSQL drivers in the Unix environments and MySQL, Oracle8 and ODBC in the Windows environment.
WWW: http://dbconnect.sourceforge.net/
Programs to convert .dbf files to MySQL tables and vice versa
Chris D. Faulhaber [jedgar@FreeBSD.org]
GtkSQL is a graphical query tool for PostgreSQL/MySQL. You can work on multiple queries simultaneously:
WWW: http://membres.lycos.fr/bbrox/GtkSQL/
libdbi implements a database-independent abstraction layer in C, similar to the DBI/DBD layer in Perl. Writing one generic set of code, programmers can leverage the power of multiple databases and multiple simultaneous database connections by using this framework.
WWW: http://libdbi.sourceforge.net/
GNU Data Access (GDA) is an attempt to provide uniform access to different kinds of data sources (databases, information servers, mail spools, etc).
It is a complete architecture that provides all you need to access your data, defined by a set of CORBA interfaces as generic as possible (but very powerful at the same time) so that any kind of data source can be accessed through them.
libgda is an interface to the GDA architecture, providing a nice wrapper around the CORBA interfaces, for both the client and the server parts. It also provides a bunch of tools to help you both in the development and management of your data sources, all done through the GDA model's set of CORBA interfaces.
libgda was part of the GNOME-DB project, but has been separated from it to allow non-GNOME applications to be developed based on it.
WWW: http://www.gnome-db.org/
iODBC (intrinsic Open Database Connectivity) is an ODBC driver manager that is compatible with the ODBC 2.x and 3.x specifications. It performs the standard tasks of a driver manager, i.e. driver loading, parameter and function sequence checking, driver function invocation, etc.
Applications linked with the iODBC driver manager will be able - through ODBC function calls - to access simultaneously different types of data sources within one process through suitable ODBC drivers.
iODBC is freely redistributable under either the GNU Library General Public Licence (LGPL) or the BSD licence.
WWW: http://www.iodbc.org/
Authors: [iodbc@openlinksw.com]
Libodbc++ aims to be a complete C++ development environment for data source (typically SQL database) access. It exists in the form of a class library and a set of tools. Libodbc++ currently provides a subset of the JDBC 2.0 specification functionality.
Libodbc++ runs on top of ODBC, i.e. it needs to be compiled with support for an ODBC driver manager. It currently supports either iODBC or unixODBC. This port allows the user to select which driver manager to use via a build-time variable definition - see the comments in the Makefile for further details.
WWW: http://orcane.net/freeodbc++/
Johann Visagie [wjv@FreeBSD.org]
This is libsdb, the simple database library, which provides a way to support multiple database management systems in an application with negligeable overhead, in terms of code as well as system resources.
Supported databases:
WWW: http://siag.nu/libsdb/
From udbc.doc: WHAT IS UDBC?
UDBC is OpenLink's acronym for Universal DataBase Connectivity. In short, UDBC is the merge between the X/Open - SAG interface and the Microsoft ODBC interface for client database applications.
UDBC was developped to enable software engineers to rapidly develop database independent applications without being concerned about issues like portability, network programming and database specific interfacing problems.
WWW: http://www.openlinksw.com/
Grosbein eugen@grosbein.pp.ru
Mysql++ is a complex C++ API for Mysql (And other SQL Databases Soon). The goal of this API is too make working with Queries as easy as working with other STL Containers.
WWW: http://www.mysql.com/download_mysql++.html
The perl script mysql2pgsql can be used to convert MySQL database dumps to a -compatible format (so the data can be imported into PostgreSQL). This can be useful if you are switching from MySQL to PostgreSQL and you have quite a bit of data in your MySQL databases.
WWW: http://www.rot13.org/~dpavlin/projects.html
Pete petef@databits.net
Class::DBI provides a convenient abstraction layer to a database.
It not only provides a simple database to object mapping layer, but can be used to implement several higher order database functions (triggers, referential integrity, cascading delete etc.), at the application level, rather than at the database.
This is particularly useful when using a database which doesn't support these (such as MySQL), or when you would like your code to be portable across multiple databases which might implement these things in different ways.
WWW: http://search.cpan.org/search?dist=Class-DBI
Sergey Skvortsov skv@FreeBSD.org
The DBI interface allows perl programs to use DBD (Database Definition) drivers with a common set of routines. A program can then (theoretically) change from using mSQL to Oracle (for example) without changing the entire program around.
This DBI interface is not yet fully specified. The current development work is focused on writing drivers, such as DBD::Oracle, which also implement emulations of old perl4 database interfaces, e.g., oraperl. This strategy enables the DBI and drivers to serve a useful purpose whilst allowing the real interface to evolve with experience behind the emulation interface.
WWW: http://forteviot.symbolstone.org/technology/perl/DBI/
Msql.pm and DBD::mSQL implement two different approaches to communicate with an mSQL server. DBD::mSQL is built upon the DBI, the generic Perl Database Interface. It brings you an identical interface to a broad variety of databases and is in this regard comparable to ODBC.
The advantage of the DBI approach is portability and interoperability. Msql.pm is the elder species. It was written before DBI was available but it was inspired by an early draft of the DBI specification. As it has been circulating longer it is more mature and pretty stable. It's also more complete than DBD::mSQL.
Some day in the future DBD::mSQL will probably be the clearly superior competitor in this package. Today you have to decide on your own about the trade-offs.
This is a DBI-for-Ruby. It is designed to behave like the DBI you know from Perl.
WWW: http://ruby-dbi.sourceforge.net/
Authors: Rainer Perl [rainer.perl@sprytech.com],
Michael Neumann [neumann@s-direktnet.de]
SQL Relay is a persistent database connection pooling, proxying and load balancing system for Unix and Linux supporting ODBC, Oracle, MySQL, mSQL, PostgreSQL, Sybase, MS SQL Server, IBM DB2, Interbase, Lago and SQLite with C, C++, Perl, Perl-DBD, Python, Python-DB, Zope, PHP, Ruby and Java APIs, command line clients, a GUI configuration tool and extensive documentation.
The APIs support advanced database operations such as bind variables, multi-row fetches, client side result set caching and suspended transactions. It is ideal for speeding up database-driven web-based applications, accessing databases from unsupported platforms, migrating between databases, distributing access to replicated databases and throttling database access.
WWW: http://sqlrelay.sourceforge.net/
The sql package adds the command sql to tcl. The author's intention is to build generic database interface for TCL, but currently he only supports MySQL.
The author's web-site is: WWW: http://sourceforge.net/projects/tcl-sql/
All content on this site is Copyright 2001
- 2003 by Bill Nicholls
All Rights Reserved