Resolve "old_name column should be dropped eventually once the duplicate field name migration is OK"
requested to merge 536-old_name-column-should-be-dropped-eventually-once-the-duplicate-field-name-migration-is-ok into develop
Merge Request Checklist
-
changelog.md has been updated if required -
Documentation has been updated -
Quality Standards are met -
The UI/UX has been updated following UI Style Guide -
The redoc API pages have been updated for any REST API changes -
The per database user API docs page has been updated for any REST API changes made to endpoints which can be accessed via a user created token -
Has performance been considered and tested when appropriate? Ideally Baserow should be performant when working with hundreds of thousands of rows -
New/Changed Premium features are separated correctly in the premium folder -
There are tests for and it has been checked that any changed/new django ORM code is sensible, doesn't perform N queries and that table models are not generated needlessly or generated with all columns when only a few are needed.
Closes #536 (closed)
Edited by Bram Wiepjes