Make sure that our pickling process is robust against future changes #104
Labels
good first issue
Good for newcomers
help wanted
Extra attention is needed
hygiene
P2
Nice to have or need to have but in the future
Right now we rely a lot of pickled columns via SQLAlchemy (via type decorators).
Changes include:
It's probably important before we start supporting real customers to make sure that the pickling process is robust and backward compatible.
I think strings are more robust against these software changes but might be slower? Something to consider.
The text was updated successfully, but these errors were encountered: