This may be useful?
http://debuggable.com/posts/unlimited-model-fields-expandable-behavior:48428c2e-9a88-47ec-ae8e-77a64834cda3
On Apr 27, 4:08 am, turbo2ltr wrote:
> Thanks, This is precisely the schema I was going to use. I guess I'm
> not quite sure what I'm askingor maybe it's that I a
Thanks, This is precisely the schema I was going to use. I guess I'm
not quite sure what I'm askingor maybe it's that I already know
the answer.. heh.
Guess I'll just play with it and see what I come up with...I think my
concern is more around building the view. With the right
relationships, i
Cake relies heavily on pre-defined and configured schemas... for a system you
describe you might create a relation (table) called "user_defined_attributes"
with a schema like:
table name: user_defined_attributes
id (PK)
user_id (FK to your user)
attrb_title
attrb_description
table name: user_e
I'm working on a system that needs to allow users to add their own
attributes to the DB. For instance if you had a movies database, I
need to allow the user to go into the attribute configuration and add
"genre" which would allow every record in the movie DB to have a genre
field. When they view a