Re: Which approach is better?

[weitat chok]

Bob Field Wrote:
-------------------------------------------------------
> I'd go with case 2, you have greater flexibility,
> you can add settings without changing your
> database design.

But all those setting, jz like a toggle, on/off, which mean if setting A for campaign 5 is "on", then perform one of the operation, and skip for other with setting A = off, then the same theory apply to other setting, then, finally, come out more than 100 tables [not all related setting :p ]

Coz, we maybe hv student, then 5 setting, campaign, 6 setting, but for those setting can actually be embedded inside student or campaign which only add in more field for them.

So, as a software designer, i always struggle with myself, and dono which is the better solution

Thanks