-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bugfix 367 postgres missing column handling #370
Bugfix 367 postgres missing column handling #370
Conversation
The error message in postgres changed, so the handling had to be adapted to retreive the missing column.
Newly created column and table names are now logged.
I am testing it currently with a new download. It seems like the new columns could be arranged in orm.py . API and xml column names are slightly different. For instance:
|
Does the failing test mean there are new columns again?
|
No, I deleted that column because it was not in the documentation. But it comes from the API download apparently, so we need to reintroduce it. |
API column name remains and bulk column name is renamed
Does this mean there were new columns added to the XML? Or API? - in addtion to #351? |
New columns were added to XML, which were undergoing because of automatic column adding as error handling. This handling was not working with local postgres databases apparently. |
No description provided.