Re: how to link different but related tables

On 03/13/2016 03:11 PM, Jerry Stuckle wrote:
>> Or (without eval), putting all different actions in a big switch/case:
>> >
>> >switch($product_type) {
>> >case 'dematerialized':
>> > // Actions to build html code related to dematerialized product
>> > break;
>> >case 'physical':
>> > // Idem for physical items
>> > break;
>> >...
>> >}
>> >
> Terrible. Code should never depend on database design.
>

Thanks everyone for hints/info.

I still have one question, I don't really understand the above comment.

I do understand that a database's purpose is to store information. So I think what Jerry means is that an application design shouldn't be dictated by the design of the database.

Maybe keep the database design as "generic" as possible so as to allow a maximum of "liberty" in the thinking of the application. Separate data storage and logic.

I think that's the idea behind this comment.

Nevertheless, I still don't understand because those 2 parts are closely related.

I have to take actions that will depend on the kind of product sold (like send a parcel or provide a file link). And that info has to be in the database.

Anything I'm missing? Received on Sun Mar 20 2016 - 22:14:08 CET