Re: storing payment packages

[Dimitris Papageorgiou]

I mean something different...I will try to explain.
In a web app(non-free) there are paid packages which the user selects when subscribed.

Every package is accompanied by some attributes,,,the price/month and the the features.

Given the fact that each business user will have selected one package how am I going to store this?

I have a table where business users are stored(name etc)

So all in all there are two questions to be addressed here...
Is a table needed to store the features of the packages since these are fixed(features will be added from time to time)...

If the above answer is true then I suppose a column must be added to the business user table that will indicate which package is chosen.

If no table is created for the packages than I assume a col(ENUM) must be added again to the business users table indicating again which package is chosen.

I am describing 2 options above.

What do you think?Unless you have to propose a 3rd or 4th etc.