Changes between Initial Version and Version 1 of Ticket #35422, comment 3


Ignore:
Timestamp:
May 2, 2024, 11:31:14 AM (7 months ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #35422, comment 3

    initial v1  
    11I don't think the problem is specific to SQLite.
    22
    3 The non-invasive back portable solution I can think of is for `FieldError` to be caught and also result in a `ValueError` pointing out that the generated field must be removed first.
     3The non-invasive back portable solution I can think of is for `FieldError` to be caught and also result in a `ValueError` [https://github.com/django/django/blob/39828fa7786a805f7a542abb929f352d3c5b722c/django/db/backends/base/schema.py#L871-L882 pointing out that the generated field must be removed first].
     4
     5In other words, if we can't generate the SQL for the old field anymore but we can for the new one then it was certainly changes and the same lack of alteration support limitation applies.
Back to Top