In web2py you can do something like:
# define a table 'meta' that describes another table 'from_meta'
db.define_table('meta',Field('colname'),Field('coltype'))
# make sure it contains something
if not db(db.meta.id>0).count()
db.meta.insert(colname='your_name',coltype='string'))
# define from_meta based on the content of table meta
meta = db(db.meta.id>0).select()
db.define_table('from_meta',*[Field(m.colname,m.coltype) for m in
meta],migrate=True)
as you edit records in 'meta', table 'from_meta' is automatically
altered accordingly. you do not need any other code. T3 uses this
mechanism.
This is one of the coolest things I like in the DAL. Try do this in
any other Python web framework.
Massimo
On Apr 10, 11:53 pm, Marc Dojka <[email protected]> wrote:
> I'm thinking of switching a site from php to python on web2py, however
> I've got a question on its mysql support. I'm trying to figure out
> how web2py handles tables where the column layout isn't fixed.
> Meaning that it's possible for columns to be created, used, and
> deleted by the app while it's running. Currently I assign api names
> to these columns (ms1, ms2, ...). There is a seperate table that
> tells the app some information about these columns (and that they
> exist). Everything works great in php land. Let me know. Thanks.
--
To unsubscribe, reply using "remove me" as the subject.
