Timeline for answer to When did developers start making normalized relational databases? by Matthieu
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 18, 2011 at 21:14 | comment | added | Matthieu | @Peter Turner : consistency vs evolution - that's almost always a tough one. Especially with large enough code base and different views regarding architecture inside the team. | |
| Jul 18, 2011 at 19:36 | comment | added | Peter Turner | @Jeff O, there's a difference between sticking out and writing code to easily work with databases. I've had more trouble writing code to use my own tables in a general way because I write the code to use the pre-existing core tables first. For instance, if I have some ID that is the primary key in one table, an a part of the primary key in another table where I'd have made it a foreign key. I can't depend on autoinc and I can't insert without checking all the keys. The way they write code is OK (meaning all problems can be solved with extra code) but by no means optimal. | |
| Jul 18, 2011 at 19:28 | comment | added | JeffO | @Peter Turner - do you want to do it right or be like everyone else? They should stick out; so what. | |
| Jul 18, 2011 at 19:05 | comment | added | Peter Turner | I can live with never-normalized databases, the real problem is when I write my own tables and I want them to be normalized, they stick out like a sore thumb because they don't fit the mold (i.e. there is usually only one primary key instead of 4-5) | |
| Jul 18, 2011 at 19:02 | history | answered | Matthieu | CC BY-SA 3.0 |