Database design thoughts

[Guard Dog]

Hey guys,

I know some of you are probably adept at this, hopefully I can get some good advice. I'm looking at creating a new datastructure and I want it to be GOOD for now and future query-ability.

The question is this... Would you have a Taxonomy table similar to Wordpress or divide into a bunch of sub-tables?

For example, let's just use something we know.. Casinos:

I could have a main table:

TableName: Casinos
Fields: casino_uid, casino_platform_uid, casino_launchdate, casino_closedate, casino_license

TableName: Software
Fields: casino_uid, software_name

TableName: Payment
Fields: payment_uid, payment_method

simple enough. Now, I want to associate 'software' to it (NYX, MGS, Rival, etc..). And then I want to associate 'payment methods' to it (Neteller, ECO, Paypal, etc..)

Do you create:

TableName: BigTaxonomy
Fields: taxonomy_uid, field, field_uid, field_value

or

TableName: Software_Taxonomy
Fields: casino_uid, software_uid

TableName: PaymentMethods_Taxonomy
Fields: casino_uid, payment_uid



Wodpress uses a large Taxonomy table... it would clean things up - but couldn't it get large and un-wieldy?

 

[TheGamblingGuru]

Why not just use a php coded widget for all that? Cats, Tags, Affiliate_Tags, xxxxxx etc etc.

Then build the table within the same php widget various different ways.

Just curious?

____
____

 

[Guard Dog]

If I were doing Wordpress, I might try it. But this database structure is much, much larger that this and more complicated. I'm just trying to think the best way to go about it. It would be tough to find a plug-in that would do what I need to be honest. Probably take a lot of re-coding to make it fit. Imagine I have about 20 tables where I need multiples (you know... like if I had a casino and 10 software providers for slots.. or 10 payment types). Now think of having at least 20 things like that Gets exponential pretty quick.

 

[TheGamblingGuru]

Yea, if not using Wordpress I can see your point there.

____
____