Libgda's databases adaptaters are called providers and this page attempts to give a list of the currently supported database types and the limitations.
Providers status |
|||
Database provider |
Compiles? |
Status |
Remarks |
Access (.MDB files) |
Yes |
Functional, read only mode |
Uses the MDB Tools library to access the .MDB files, and is limited by its features |
Berkeley DB |
Yes |
Fully functionnal |
Access to the key/value Berkeley DB database |
Berkeley DB SQL |
Yes |
Fully functionnal |
Access to any Berkeley DB using the new SQL API, only in upcoming 4.2 version |
Firebird |
No |
Outdated |
|
IBM DB2 |
No |
Outdated |
|
TDS (Microsoft SQL Server and Sybase) |
No |
Outdated |
Uses the FreeTDS library |
mSQL |
No |
Outdated |
|
MySQL |
Yes |
Fully functional |
For version 5.0.x |
ODBC |
No |
Outdated |
Features limited by ODBC |
Oracle |
Yes |
Fully functionnal |
Only in upcoming 4.2 version |
PostgreSQL |
Yes |
Fully functional |
For versions >= 8 |
SQLite |
Yes |
Fully functional |
Uses an embedded or external version if possible |
Sybase |
No |
Outdated |
Uses the Sybase API |
Xbase |
No |
Outdated |
|
JDBC |
Yes |
Fully functionnal |
Generic wrapper of any database accessed using JDBC |
Web |
Yes |
Fully functionnal |
Generic access to databases hosted behind a web server (some PHP scripts must be installed on the web server and available connections must be configured), only in upcoming 4.2 version |
You can help improve this table's accuracy by testing libgda with your database.
DISCLAIMER: there is no guarantee that this software functions correctly or that it will not destroy or damage your data. You are warned: Don't test on production servers.