On 08/25/2016 04:37 PM, Seth P wrote:
If I understand what you're saying, the problem is that set
_creation_order() specifies an ordering across all columns from all
mixins. But shouldn't it suffice to specify the "local" ordering of the
columns within a given mixin, and then process the
If I understand what you're saying, the problem is that set _creation_order()
specifies an ordering across all columns from all mixins. But shouldn't it
suffice to specify the "local" ordering of the columns within a given mixin,
and then process the mixins in __mro__ order?
(FWIW I worked
the @declarative_attr object would need util.set_creation_order()
applied and the _MapperConfig._scan_attributes() would need to take this
into account. However, it would not behave well across multiple mixins.
The mixins must be scanned in __mro__ order first. So it would be of
limited
I was just bitten by this issue. Is it still the case that there is no way to
specify the order of two columns declared in a mixin using @declared_attr?
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop
On Jul 21, 2011, at 4:07 PM, Hans-Martin v. Gaudecker wrote:
Hi,
I am creating a bunch of columns by means of the declared_attr decorator
since many of them contain foreign keys. Similar to the issue in this thread
[1] from a year ago, it seems that the column order is not preserved. To
