Re:BlurHash: Algorithm to generate compact representation of...
by hinkley on Thursday February 20, 2020 @05:26PM
(#22379221)
This only indicates that you have worked with a better class of DBA than I have.
"Why are we creating new table and foreign key relationships for this single bit of data?"
"Oh, because we aren't allowed to add any columns to <the appropriate table>"
"Wait. None?"
"None."
(Only the last conversation I had of this sort involved MySQL, which was notoriously bad at adding columns to live tables)
The cost of 5 extra joins for all business activities is going to outweigh whatever you think you have going on with that original table.
I think in some ways the situation was improved by expanding developer responsibilities to include these tasks rather than having a dedicated role. When you have to deal with the consequences of your own decisions instead of someone else being responsible, some activities won't be done at all, while others will go more smoothly. Without the database being personified, it's more of a doing something for somebody (else) instead of doing it to somebody.
"Why are we creating new table and foreign key relationships for this single bit of data?"
"Oh, because we aren't allowed to add any columns to <the appropriate table>"
"Wait. None?"
"None."
(Only the last conversation I had of this sort involved MySQL, which was notoriously bad at adding columns to live tables)
The cost of 5 extra joins for all business activities is going to outweigh whatever you think you have going on with that original table.
I think in some ways the situation was improved by expanding developer responsibilities to include these tasks rather than having a dedicated role. When you have to deal with the consequences of your own decisions instead of someone else being responsible, some activities won't be done at all, while others will go more smoothly. Without the database being personified, it's more of a doing something for somebody (else) instead of doing it to somebody.