3 ms·
> Also persisting stuff in customer DBs that depends on class names (and reflection) is nice source of terror. We do that but with XML files, most of our table
by Zababa 5y ago
> Also persisting stuff in customer DBs that depends on class names (and reflection) is nice source of terror.
We do that but with XML files, most of our tables are dynamically generated. I'm a bit scared every time I touch this part.
- splittingTimes 5y agoWe have a whole framework that handles migrations of costumer DBs after updates. But when you don't even know that your changed class gets persistent (because of spaghetti inheritance/type hierarchy) and you do not enter it in the migration scripts, you duck up.