Schema history for better error messages

[lars-reimann]

Is your feature request related to a problem?

After a long chain of transformations on a Table it can be easy to access a column that no longer exists.

Desired solution

• A Schema could store a chain of previous Schemas and the transformation that lead from one to the next. This can include
  • Removal of a column
  • Replacement of one or more columns by one or more other columns
  • Addition of a column (not needed for this feature)
  • Changes of a column (not needed for this feature)
• When the user accesses a column that doesn't exist, we can trace the chain back to figure out whether the column was removed or replaced at some point. If it was, we can include this in the error message. Ideally we should also point to the exact location in the code of the user where that happened.

Possible alternatives (optional)

No response

Screenshots (optional)

No response

Additional Context (optional)

No response

[lars-reimann]

This won't be worked on, since it's too much effort to implement and to keep it running as more operations are added to the Table class.