4 ms·
I think making a previously-static node polymorphic in a way that doesn't drop any required field is actually quite rare. But also, I just think the first one i
by FeepingCreature 5y ago
I think making a previously-static node polymorphic in a way that doesn't drop any required field is actually quite rare. But also, I just think the first one is better.
- stickfigure 5y agoIt's much easier to migrate adding/dropping fields than to make structural changes. Adding/dropping fields is the easiest form of migration. I honestly have a hard time believing that you prefer: asset.Asset.owner.Person.contact.Address.street1 to: asset.owner.contact.street1 If so, I think you should really announce this first and foremost in your article so that everyone can take a proper measure of your sanity :-)
- FeepingCreature 5y agoI mean, I don't actually believe you that all those levels are polymorphic. :-) IME, we have one, at most two polymorphic fields per message. And for an example chosen deliberately to be annoying, I still like the deeper tree better- at least it advertises that something unusual is going on.