Message 60450

Author
nicoe
Date
2020-09-28.18:10:25
Message id
60450

Content

In order to fix issue7962 we introduced a change that drop and recreate the columns month and weekday even if there is no migration to handle.

When executing the migration a great number of time we reach the maximum number of column permitted on a postgresql because postgres never removes the dropped column but hides it: https://nerderati.com/2017/01/03/postgresql-tables-can-have-at-most-1600-columns/

I propose to add to the backend table handler a way to retrieve the column type and change the test to check if the column should be dropped or not.
History
Date User Action Args
2020-09-28 18:10:25nicoesetrecipients: + jcavallo
2020-09-28 18:10:25nicoesetmessageid: <1601309425.54.0.842874802352.issue9645@tryton.org>
2020-09-28 18:10:25nicoelinkissue9645 messages
2020-09-28 18:10:25nicoecreate

Showing 10 items. Show all history (warning: this could be VERY long)