You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that reflected tables store the unique constraint under Table.constraints, not in the Table.columnColumn objects. When reflecting a table, Column.unique will always be None.
This means that this ingested table definition will trigger a swap:
Currently, live tables are reflected, then checked column by column for identity based on several pieces of data, including
Column.unique
.pg-bulk-ingest/pg_bulk_ingest/__init__.py
Lines 139 to 146 in 41bb283
The problem is that reflected tables store the unique constraint under
Table.constraints
, not in theTable.column
Column
objects. When reflecting a table,Column.unique
will always beNone
.This means that this ingested table definition will trigger a swap:
But this won't:
Even though they're functionally identical.
The text was updated successfully, but these errors were encountered: