noted in #9294 and now in the whats new notes in 037884e , we can add a new indicator to mapped_column() specifically that tells Declarative how to order columns when creating Table.
Why mapped_column()? Because this is ORM specific. Column / Table has no "sorting", the order is the order in which Column objects are placed into the Table.
Propose mapped_column.sort_order, which accepts any object type and uses it to apply sorted(). Users can specify integers, strings, floats, or any custom Python object that has an __lt__() method, so that any scheme can be created. which is an int value. By default all columns have the value of 0
Declarative would record this sort order and apply it specifically within the _setup_table() method.
noted in #9294 and now in the whats new notes in 037884e , we can add a new indicator to
mapped_column()specifically that tells Declarative how to order columns when creating Table.Why mapped_column()? Because this is ORM specific. Column / Table has no "sorting", the order is the order in which Column objects are placed into the Table.
Propose
mapped_column.sort_order,which accepts any object type and uses it to applywhich is an int value. By default all columns have the value of 0sorted(). Users can specify integers, strings, floats, or any custom Python object that has an__lt__()method, so that any scheme can be created.Declarative would record this sort order and apply it specifically within the
_setup_table()method.