well this one will probably end up somewhere around 30 rows
and if i actually get around to populating it then it should have anywhere from 100-1000 rows... i'll try it and if it borks then i'll break it up a bit
( ,
Wed 2 Feb 2005, 11:38,
archived)
pah... i'm not a database person... they're far too organised
i'm still slightly miffed that i'm expected to use postgres for all my DB work this year... i like the unscariness of mysql
( ,
Wed 2 Feb 2005, 11:42,
archived)
there`s not a moleste difference actually; just slightly different syntaxsisisisisisis
plus postgres supports err triggers and stuff from what I remember (which ain`t much.. mysql all the way for me .. and oracle)
( ,
Wed 2 Feb 2005, 11:44,
archived)
dBase IV
pronounced "dee basssssss" by my old database teacher - the same bloke who looked like Frank Drebin, and who pronounced MS-DOS as "emm ess doooooooooooos"
"- don`t forget to do your regular [backup] dumps"
( ,
Wed 2 Feb 2005, 11:56,
archived)
"- don`t forget to do your regular [backup] dumps"
Normalisation as a general rule
actually 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.
( ,
Wed 2 Feb 2005, 11:49,
archived)
It does very well at reducing the amount of storage used overall in the DB though.
i can't even understand this
en.wikipedia.org/wiki/Database_normalization
darn it...
/humble undergrad
( ,
Wed 2 Feb 2005, 11:50,
archived)
darn it...
/humble undergrad
definitely
and 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
( ,
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!
( ,
Wed 2 Feb 2005, 11:54,
archived)
I say screw the database and have one moleste XML file!