It will be no problem updating manually.
New sizes and finishes are less of a problem than switching their availability on and off.
Just that the DB I am designing for the project has a lot of updating need like in the example for my question.
I will just "bundle" an UPDATE statement to every relevant point in the application.
It would have been nice to have a database that could keep data-integrity by itself.
I looked into triggers, now that you mentioned them.
I learned to set them up in no time and they are exactly what I need. They are a very simple form of an event system which is the "spine" for OOP, great!
Only working in the dark would indeed be masochistic, if that is what you meant.
Can you recommend a good, perhaps even free IDE for conveniently developing and maintaining a fair amount of triggers in MySQL?
I found phpMyIDE but have not idea if it is any good.
Do you think there are other reasons to feel masochistic for working with triggers?
Just too bad that a lot of hosting providers do not allow to connect to databases remotely in shared hosting environments.
I am still working with both phpMyAdmin and Heidi and phpMyAdmin does not include the SQL for the triggers when exporting a database to a SQL file.