3 ms·
There is an argument for you to be able to decide the packing yourself. Let’s say you have a few variable length fields but you know one of them will be accesse
by klysm 4y ago
There is an argument for you to be able to decide the packing yourself. Let’s say you have a few variable length fields but you know one of them will be accessed much more frequently. You can put that one first. The database won’t know that information.
- gleenn 4y agoSeems like it couldn't hurt to do the initial schema load in an optimal way, and if you add and drop columns to oblivion then that sucks but most people are add-only for databases of any sufficient size in general.
- jagged-chisel 4y agoI can see it being optional.
- dietr1ch 4y agoI just want to specify an order that makes reading easier, not one that would work nicely, I'm not an optimizing compiler, don't make me do that work. There's sometimes need for control in performance-critical things, but that needs an escape hatch instead of providing everyone with an implicit tool they don't even know they have. The same applies to struct packing in I guess most compiled languages and using the order to define ABIs.