Subject: Re: How to architect question: custom fields
I can tell you what we have done when faced with a similar problem,
maybe it
will help you out. We create a table that holds the question, client
id,
and field type (select, numeric, text, etc.). There is another table
that
will store
I can tell you what we have done when faced with a similar problem, maybe it
will help you out. We create a table that holds the question, client id,
and field type (select, numeric, text, etc.). There is another table that
will store the values if a field is select type, we call this the lookup
I've got a similar setup in my system.
This may not be the BEST way to do it, but it works fine for me.
For any given entity, I have a main data table, that always has the same
fields.
I also create a custom data table associated with that main entity
table. The table names are similar, i.e.
We have an app, and differing clients are layering on top of the system,
and each would like a few custom questions asked.
So, I am faced with creating this and am wondering if anyone had some
experience they can share. Basically create an add-on to allow custom
fields.
I created a
4 matches
Mail list logo
