Changes between Initial Version and Version 2 of Ticket #30412


Ignore:
Timestamp:
04/26/19 19:54:32 (3 years ago)
Author:
Michael Spallino
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30412

    • Property Needs tests set
  • Ticket #30412 – Description

    initial v2  
    11Django is incorrectly including the fully qualified field name(e.g. “my_table”.”my_field”) in part of the check constraint. This only appears to happen when there is a combination of OR and AND clauses in the CheckConstraint.
    22
    3 Including the fully qualified field name fails the migration because when we drop the old table and swap the name of the staging table in place, the constraint fails with a malformed schema exception (on sqlite) saying that the field doesn’t exist on the table. Here is an example of this behavior:
     3Including the fully qualified field name fails the migration because when we drop the old table and swap the name of the staging table in place, the constraint fails with a malformed schema exception (on sqlite) saying that the field doesn’t exist on the table. It appears that this has to do with the AND clause items using Col while the OR clause uses SimpleCol. Here is an example of this behavior:
    44
    55
Back to Top