Changes between Initial Version and Version 2 of Ticket #34568


Ignore:
Timestamp:
May 16, 2023, 5:00:55 AM (19 months ago)
Author:
David Sanders
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34568 – Description

    initial v2  
    2121
    2222My opinion is that it shouldn't as it violates the principle of least astonishment ''even though the `--name` argument wasn't supplied''.
     23
     24
     25EDIT:
     26This is my first time using --update and here are a few other observations which could indicate that it requires broader discussion:
     27
     28 - It doesn't utilise the --name argument so it's impossible to customise the name during --update
     29 - It'd be nice to provide --no-optimize option to --update, here's my use-case: 3-step non-null field addition. After doing nullable step 1, elidable data migration step 2, I want to merge the step 3 non-null update into the migration but --update optimizes this into a single step.
     30
     31Perhaps --update requires a rethink?
Back to Top