Changes between Initial Version and Version 1 of Ticket #36364, comment 1


Ignore:
Timestamp:
May 3, 2025, 12:09:52 PM (4 months ago)
Author:
Jacob Walls

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36364, comment 1

    initial v1  
    33> Django doesn’t support migrating to, or from, a composite primary key after the table is created.
    44
    5 Perhaps this is an "optimization" ticket then.
     5... although the failure here is less about migrating away from the composite primary key and more about migrating away from the ForeignObject shadowing it. (I feel like the example could likely be adjusted to leave the CPK alone).
     6
     7Perhaps this is an "optimization" ticket then?
Back to Top