[RESOLVED] probably easy question - re database structure

christillis

Hi there all,

Just an easy question for you all.

Time is precious for everyone (apart from me), so simple answers are fine - don't wish to waste anyones time.

In a scenario where records would be duplicated, is it best to do this, where one table is used:

Or this, where a table is used for each reference:

I just figure this latter version would be better for doing maths functions on the INT's for example. Or to allow 'ticking off' records.

Many thanks!

Chris

laserlight

It may be neither. One way is to think in terms of entities and relationships. What are the entities that you are working with? These could be represented as tables.

EDIT:
Actually, I might have misinterpreted your hand drawn tables, in which case it is possible that the "one table for all projects" is the way to go.

Also, read the PHP Builder article on Database Normalization and Design Techniques.

christillis

Hi laserlight,

thanks for replying, much appreciated.

I've read about Database Normalization and Design Techniques already, but I'll give this a version a go to see if it sinks in!

I was tempted to go with the one table per project option, merely because it would be easier to script calls for all the contents...but that is in my very newbee opinion!

Thanks, Chris