I have a database that is well-normalized. I have a group whose refusal to work with me is resulting in me being forced to ignore the normalization of my database and the potential error-catching. Thus, how do I neuter a well-normalized database?
You need to get your manager / director / CTO to lean very heavily on this other group and explain to them (using very small words) that their refusal to work within the defined process is counter-productive and will shoot them in the foot in the very near future.
Barring that, drop and reload the database every time you get a new file. If nothing else, it'll be a good goad on the group. (And, it'll feel amazing every time you know that group just lost data. *mhwahahaha*)
In other words, there is no good technical fix for people who refuse to follow the good technical solution that is already provided.
------
We are the carpenters and bricklayers of the Information Age.
The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6
... strings and arrays will suffice. As they are easily available as native data types in any sane language, ... - blokhead, speaking on evolutionary algorithms
Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.
In reply to Neuter the normalized database
by dragonchild
in thread (OT) database design question
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |