[FIX] P3: initialisation order of columns

Python 3's hash randomisation means columns can be iterated — and thus
initialised — in any order (within a given model/override anyway),
which means there can be an implicit dependency on column
initialisation order e.g. (res.company).currency_id has a default
which fetches the currency_id of the company_id of the administrator,
and res.company has a _order=sequence,name, if the currency_id field
is created before the sequence the SELECT query will blow up as the
sequence column will not exist yet.

Attempt to always manipulate (iterate & initialize) fields based on
their order of definition using a global sequence number.

0 files changed, 0 insertions, 0 deletions