Reimplementation for Django 4.2+ Compatibility and Security Enhancement

[shimizukawa]

Current state

• To maintain compatibility of django-redshift-backend, the decision was made to vendor the PostgreSQL backend and Django codebase from Django 4.0 codebase.
• While this approach temporarily ensured compatibility with Redshift, it has resulted in an ongoing situation where new features and fixes from the latest Django versions cannot be incorporated

Why is it in its current state?

• Redshift is based on the PostgreSQL 8.0.4 interface.
• Django 4.1 and later versions have dropped compatibility with PostgreSQL 10 and below.

How to fix the issues

• Re-implement this backend independently without relying on the Postgres backend.

Tasks

Tasks

Beta Give feedback

1. Investigate the database backend interface for Django 4.2+
2. Investigate the Psycopg3 compatibility with Redshift (postgres 8.0.4) interface
3. Trying https://github.com/aws/amazon-redshift-python-driver
4. Design the new Redshift backend
5. Implement coding and unit tests
6. Removes the unsupported "ON CONFLICT DO NOTHING" clause #103
   +0
7. add distinct on support #104
   +0
8. Conduct compatibility tests with existing applications
9. Update documentation

[anentropic]

psycopg/psycopg#122

or should it use:
https://github.com/aws/amazon-redshift-python-driver
?

[shimizukawa]

or should it use: https://github.com/aws/amazon-redshift-python-driver ?

It would be worth trying the amazon-redshift-python-driver. Thank you.