Projects

DBI

The DBI module enables your Perl applications to access multiple database types transparently. You can connect to a large number of databases, including MySQL, MSSQL, Oracle, Informix, Sybase, ODBC etc. without having to know the different underlying interfaces of each. The API defined by DBI will work on all these database types and many more.

dibi

dibi is tiny 'n' smart database abstraction layer for PHP 5. It is designed with simplicity in mind. dibi is free (released under the terms of the dibi license). You can use it to develop either open source or commerical applications.

SOCI

The database access library for C++ programmers that provides the illusion of embedding SQL in regular C++ code, staying entirely within the C++ standard.

DBD::ODBC

ODBC Driver for perl DBI. Provides the Perl DBI::DBD interface to ODBC drivers allowing Perl access to any database which has an ODBC driver.

django-pyodbc

DescriptionA Django external database backend for MS SQL Server that uses ODBC by employing the pyodbc library, supports SQL Server 2000 and 2005. Pyodbc seems to be a mature, viable way to access SQL Server from Python in multiple platforms and is actively maintained. It's also used by ... [More] SQLAlchemy for SQL Server connections. ImportantIf you are following Django trunk development and have revision 10026 or newer, the minimal development revision of django-pyodbc trunk you need to use is r157. Also, the DATABASE_ODBC_DRIVER, DATABASE_ODBC_DSN and DATABASE_ODBC_EXTRA_PARAMS settings were migrated to the DATABASE_OPTIONS dictionary setting in this revision. This is a backward-incompatible change for setups that were using at least one of these three settings. The equivalent DATABASE_OPTIONS keys are 'driver, 'dsn' and 'extra_params' respectively. SVN trunk development follows closely Django development, so it needs a recent checkout of Django SVN trunk. On Jan 24, 2009 (r138) a django-1.0.x SVN branch was created, its main purpose is to remain compatible with the Django 1.0.x maintenance branch. See our News page. FeaturesWorks on Windows and Linux (using FreeTDS) Native Unicode support. Every string that goes in is stored as Unicode, and every string that goes out of the database is returned as Unicode. No conversion to/from intermediate encodings takes place, so things like max_length in CharField works just like expected. Limit/offset emulation supported in SQL Server 2005 and SQL Server 2000. Offset without limit emulation supported in SQL Server 2005. Both Windows Authentication (Integrated Security) and SQL Server Authentication supported. Passes most of the Django test suite. InstallationInstall pyodbc. Download django-pyodbc. Add the top directory of your django-pyodbc checkout to your PYTHONPATH. In your settings file set the DB engine to sql_server.pyodbc. ConfigurationSee Settings. Examples: On Windows, accessing SQL Server 2005: DATABASE_ENGINE = 'sql_server.pyodbc' DATABASE_NAME = 'db_name' DATABASE_USER = 'webapp' DATABASE_PASSWORD = 'sikrit' DATABASE_HOST = r'test_server\SQLEXPRESS' DATABASE_OPTIONS= { 'driver': 'SQL Native Client', 'MARS_Connection': True, }Using FreeTDS plus unixODBC on Linux/Unix, accessing SQL Server 2000: DATABASE_ENGINE = 'sql_server.pyodbc' DATABASE_NAME = 'the_database' DATABASE_USER = 'django_access' DATABASE_PASSWORD = 'guessme' DATABASE_OPTIONS = { 'driver': 'FreeTDS', 'dsn': 'MyDSN', # ODBC DSN name defined in your odbc.ini }Testing environmentsTested on: SQL Server 2005 Express SP2 and SQL Server 2000 SP4, Python 2.5 and Windows XP. SQL Server 2005, Python 2.5 and Ubuntu 8.04. Open issuesCurrently, the following parts of the Django test suite don't pass: lookup: Regular expressions are not supported out of the box by SQL Server. Only simple wildcard matching with %, _ and [] character classes. serializers: Forward references cause foreign key constraint violation. ThanksFilip Wasilewski. For his pioneering work, proving this was possible and profusely documenting the code with links to relevant vendor technical articles (Django ticket #5246). mamcxi (http://www.elmalabarista.com). For the first implementation using pymssql (Django ticket #5062). Adam Vandenber (from the django-mssql project). For code to distinguish between different Query classes when sub-classing them. All the Django core developers, especially Malcolm Tredinnick. For being an example of technical excellence and for building such an impressive community. The Oracle Django team (Matt Boersma, Ian Kelly) for some excellent ideas when it comes to implement a custom Django DB backend. [Less]

django-mssql-pyodbc

django microsoft sql server backend using pyodbc, work with django trunk, support both on Windows and Linux. It also support SQL Server 2000,2005,and up. This project base on django-pyodbc, and rewrite for django trunk (queryset-refactor).

Mini SQL Query

Mini SQL Query is a minimalist SQL query tool for multiple databases (MSSQL, MSSQL CE, SQLite, OLEDB, MS Access/Excel files etc). The tool uses a generic schema engine taking advantage of the ADO.NET providers. Mini SQL Query is also easily extended with plugins.

SOCI-Ada

SOCI-Ada is a database access library for Ada, based on the SOCI project. SOCI-Ada provides the following features of SOCI to the Ada community: * Modular design based on dynamic backend loading. Thanks to this feature, new backends implemented within the context of the main SOCI project ... [More] are immediately available for Ada programmers without any additional work. A large community of C++ users can help ensure that the new backends are well tested in a variety of environments and usage scenarios. * Native backends for major database servers ensure optimal performance and minimize configuration overhead and complexity that is usually associated with other database access methods. * Direct support for bulk operations allow to achieve high performance with queries that operate on large data sets. * Very liberal open-source license (Boost, accepted by Open Source Initiative) that encourages both commercial and non-commercial use. * Easy to use and compact interface. Currently the following database servers are directly supported via their native interfaces: * Oracle * PostgreSQL * MySQL [Less]