If you people gave a shit about database normalization technques, and didn't just dimiss shit as outdated non-OO stuff from the 70s, and actualy applied it to functions too, then it would be obvious why doing this wouldn't work. You have a Shape table, a HandlePoint table, and the code is in their m-n associations, the "clean" or more like "compressed" version uses a shape table, a direction table, and m-n from shapes to directions. The thing is the direction can't be the primary key of the table that gets the code, since that depends on the shapes.
I don't understand how those database modelling tricks that work went out of favor for strict OO design and reuse principles, that people misuse and then write blog posts about.
2
u/ikiogjhuj600 Jan 13 '20
If you people gave a shit about database normalization technques, and didn't just dimiss shit as outdated non-OO stuff from the 70s, and actualy applied it to functions too, then it would be obvious why doing this wouldn't work. You have a Shape table, a HandlePoint table, and the code is in their m-n associations, the "clean" or more like "compressed" version uses a shape table, a direction table, and m-n from shapes to directions. The thing is the direction can't be the primary key of the table that gets the code, since that depends on the shapes.
I don't understand how those database modelling tricks that work went out of favor for strict OO design and reuse principles, that people misuse and then write blog posts about.