Normalisation as a general ruleactually impacts performance on a database as the RDBMS has to process the joins, access extra tables etc etc.
It does very well at reducing the amount of storage used overall in the DB though.
(It does very well at reducing the amount of storage used overall in the DB though.
dazzla - Just blew up his shuttle and potentially lost all pr0n,
Wed 2 Feb 2005, 11:49,
archived)
i can't even understand thisen.wikipedia.org/wiki/Database_normalization
darn it...
/humble undergrad
(darn it...
/humble undergrad
lemony,
Wed 2 Feb 2005, 11:50,
archived)
i start to lose the plotafter second normal form and give up.
( dazzla - Just blew up his shuttle and potentially lost all pr0n,
Wed 2 Feb 2005, 11:53,
archived)
definitelyand a lot of normalisation is actually just common sense; relating stuff together and linking where appropriate - it works nicely with OO programming as you`re using the same approach there
(
Reckless_Rik,
Wed 2 Feb 2005, 11:57,
archived)
oh definitely - that`s why indexes were created ;)but if you`re writing object oriented code with object persistence layers, it makes no sense at all not to normalise as the data drives the design of data transfer objects and the like
I say screw the database and have one moleste XML file!
(I say screw the database and have one moleste XML file!
Reckless_Rik,
Wed 2 Feb 2005, 11:54,
archived)
fair enoughnot really had much exposure to the OO gubbins, purely dba me.
p.s. Gotta love the word filter at the moment
(p.s. Gotta love the word filter at the moment
dazzla - Just blew up his shuttle and potentially lost all pr0n,
Wed 2 Feb 2005, 11:59,
archived)