This site has been retired. For up to date information, see handbook.gnome.org or gitlab.gnome.org.


[Home] [TitleIndex] [WordIndex

How to choose between Libgda and SQLite

Libgda has been added as a new external dependency for GNOME 2.26, with now two database libraries: Libgda and SQLite.

This page offers some hints about how to make the choice between the two when writing an application which needs to store/access some data in a database.

Comparison hints

Of course if you want to either be able to access different databases types or you think you may need to in the future, Libgda is a better choice because with SQLite you can only access SQLite files. The comparison makes sense only if you want to create an SQLite database and have to decide between Libgda and SQLite to do it. Note that Libgda uses SQLite internally anyway (it's not a reimplementation) to access SQLite files.

One important thing to keep in mind is that changing from using SQLite to using Libgda (or the other way around) can be a long an painfull experience, so you need to make sure you choose the right one right from the beginning.

Common points

Here are some (more or less) common points between Libgda and SQLite:

Libgda's features SQLite does not have

SQLite is a database engine implementation, and as such it's not meant to compete feature for feature with database abstraction libraries like Libgda, ODBC or JDBC. However it's important to know what features are implemented in Libgda which you may need to implement yourself in your application if you use SQLite directly.

Those features are:


2024-10-23 11:02