Dynamically add new tables to existing databases

[FlorianK13]

If new tables are introduced by BNetzA, the current code cannot simply add them to an existing database. For example, when running db.download() and there is already a database initialized, a new table will cause an error. This should be changed, ie. new tables should be added automatically.

They should take the name from orm.py if the new table is already part of a new open-mastr release. Or they should just use the german name otherwise.

[nesnoj]

An automatic creation be great, but the value replacement (e.g. 4=biomass) should be added too.

[FlorianK13]

If only this was already implemented, we would not need to handle #572 under time pressure 🙄

[FlorianK13]

With 0.14.5 we now have at least the case that tables that are new do not result in a crash anymore. However they are still not automatically added.

[nesnoj]

Yes, let's talk about this in our JF

[nesnoj]

Notes from JF:

• Dynamic update needed
• There seems to be no way of getting the structure in machine-readable form prior to the public release. So no early adapted release is possible.
• How to proceed with orm.py?
  • Regularly parse xsd from "Beschreibung des Exports" and create PR with ORM update?
  • Get rid of orm.py - only dynamic creation
  • keep in mind: existing DB structure and CSV export