Database design: How should I add an information which can apply to several tables

Posted by Stefan on Stack Overflow See other posts from Stack Overflow or by Stefan
Published on 2010-04-05T21:25:45Z Indexed on 2010/04/05 21:33 UTC
Read the original article Hit count: 196

Filed under:
|

I am constructing a database System using Mysql, this will be an application of about 20 tables. The system contains information on farmers, we work with organic certification and need to record a lot of info for that.

In my system, there are related parent-child tables for farmers, producing years and fields/areas - it's a simple representation of the real world in which farmers farm crops on their fields.

I now need to add several status flags for each one of these levels: a farmer can be certified, or his field can be, or the specific year can be; each of these flags has several states and can occur a number of times.

The obvious solution to this would be to add a child table to every one of these tables, and define the states there.

What I wonder if there is an easier way to do this to avoid getting to many tables? Where/how would be best practise to keep that data?

© Stack Overflow or respective owner

Related posts about database

Related posts about mysql