Open Adean64 opened 2 years ago
Hi @Adean64, thanks for reporting the issue.
Immudb is compatible with postgresql wire protocol so that you can connect to it using a compatible driver. However it is not compatible on the featureset level e.g. supported types, schema queries or even some SQL syntax - such compatibility ins possible in theory but it would be a huge effort to ensure we're compatible enough to support ORMs such as the one used in django.
A much better alternative would be a custom immudb django driver - similarly to django-cockroachdb (cockroachdb is also psql wire-compatible and provides much greater feature compatibility but still failed to meet django's psql requirements).
What happened I am unsure if this is a bug, or simply outside of the design scope and use-case for immudb: I was attempting to set up immudb as a Postgres database for Django - in an attempt to be able to essentially audit any Django transaction via the immugw or immuclient auditors. However, when setting
--pgsql-server=true
,--pgsql-server-port=5432
in immudb and adding'OPTIONS': {'sslmode': 'disable'}
to the postgresql Django backend engine, I got the following error log:What you expected to happen I would not have expected the latest version of immudb to have pgsql support only up to version 9.6.
How to reproduce it (as minimally and precisely as possible) Setting
--pgsql-server=true
,--pgsql-server-port=5432
in immudb and adding'OPTIONS': {'sslmode': 'disable'}
to the postgresql Django backend engine insettings.py
of a Django project, then attempting to execute a migrate viamanage.py
will trigger this error.Environment
(and Django version 4.1.2)
Additional info (any other context about the problem) Is there a reason that the PostgreSQL version is so far behind current? Are there plans to update it, or otherwise make immudb more compatible with Django?