Normalizing the DB

[Kgaul]

I'm under the impression that the Items table can be normalized to conform to the first three rules. However before i post my thoughts on breaking up the table some i wanted to know if you had it the way it is for a reason?

second. will me breaking it up to conform to the third rule really make me unpopular with Mangoo and those who are creating programs to read/modify the items... Also will reworking this cause probs with item pc and updates (yea, i'm quite sure you guys can adjust to the new tables if you use them i just wanted to know if i should bother normalizing it?)


Kgaul

[mangoo]

I'm not sure what the "3 rules" are, but if it's just breaking the table into 3 tables, it would only take about 5 minutes to change the queries. I'm going to be gone for awhile so item editor won't be changed for the new tables until like mid December.

[Kgaul]

no worries friend enjoy your awaytime. I'm just trying to establish if i should press this. looks like i can break it into a few tables, maybe gain some speed if the tables are more 'relational'. Going to be a few weeks before i finish working this up. not alot of free time the next few weeks anyway...


Kgaul

[mangoo]

Well if you call turning in papers and studying/taking finals enjoyable, then I guess I will enjoy the away time. HAHA

[Valtin]

Normalisation of databases has the primary effect of reducing the storage space needed. In commercial development databases are quite routinely denormalised in order to get performance gains, I think that might be the case with the items table. The actual storage space of duplicated items (if any) isn't really an issue, the overhead of having to do additional joins may degrade the performance though.

[Edgar1898]

Change your own db however you like, but the official release isnt going to switch to few table