Firebird vs. H2 vs. SQLite vs. django-mysql Comparison Chart

Welcome to H2, the Java SQL database. In embedded mode, an application opens a database from within the same JVM using JDBC. This is the fastest and easiest connection mode. The disadvantage is that a database may only be open in one virtual machine (and class loader) at any time. As in all modes, both persistent and in-memory databases are supported. There is no limit on the number of database open concurrently, or on the number of open connections. The mixed mode is a combination of the embedded and the server mode. The first application that connects to a database does that in embedded mode, but also starts a server so that other applications (running in different processes or virtual machines) can concurrently access the same data. The local connections are as fast as if the database is used in just the embedded mode, while the remote connections are a bit slower.

Django-MySQL extends Django’s built-in MySQL and MariaDB support their specific features not available on other databases. A new cache backend that makes use of MySQL’s upsert statement and does compression. Named locks for easy locking of e.g. external resources. Extra checks added to Django’s check framework to ensure your Django and MySQL configurations are optimal. Django-MySQL comes with a number of extensions to QuerySet that can be installed in a number of ways - e.g. adding the QuerySetMixin to your existing QuerySet subclass.