From 0995a32cc88d464225b1fd00ffbf109b129a895a Mon Sep 17 00:00:00 2001 From: Jimmy Huguet Date: Tue, 6 Feb 2024 11:07:00 +0100 Subject: [PATCH] Fix: fix constraint creation using the wrong table and column name This was causing issue if a foreign key was pointing to another field than the remote table id --- django_redshift_backend/base.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/django_redshift_backend/base.py b/django_redshift_backend/base.py index 368f408..5160cec 100644 --- a/django_redshift_backend/base.py +++ b/django_redshift_backend/base.py @@ -205,8 +205,8 @@ def create_model(self, model): params.extend(extra_params) # FK if field.remote_field and field.db_constraint: - to_table = field.remote_field.related_model._meta.db_table - to_column = field.remote_field.related_model._meta.get_field( + to_table = field.remote_field.model._meta.db_table + to_column = field.remote_field.model._meta.get_field( field.remote_field.field_name).column if self.connection.features.supports_foreign_keys: self.deferred_sql.append(self._create_fk_sql(