Hi Phyo!!! I needed almost the same, and I found the EAV Modeling technique (http://en.wikipedia.org/wiki/Entity-attribute-value_model) useful, but due the complexity of my project I write the model as a file, I mean open the *.py, write, append.....
On Wed, Sep 28, 2011 at 4:31 PM, Phyo Arkar <[email protected]>wrote: > Here is what i was asked for, weird that i haven't see in any application > yet. > > A Dynamic Model : A dynamic table schema. > > They want a feature to add a column dynamically , for example a table do > not have comment field. they want a button to add a new field on the fly and > add the data into it. > > so when he modify a table by adding new field , That new Table model need > to store somewhere. Should i keep it inside DB ? > its gonna be weird that when his table gonna load , it will look up into db > for table defination and load it.. > > What you guys think? > > Thanks in advance > > Phyo. >
