Assume I'm building a row-based audit system.  I also want this audit
system to have one audit table/model per legitimate Django model.  So,
say I have an app.model called "wiki.article".  This would create a
"wiki_article" table.  I also want to have a "wiki_article_audit" table
keeping a full history of changes.  Now, since Django models don't
support inheritance yet, and I don't want to have to re-create every
model that I want to perform an audit on, I can instead create a dynamic
model from the original model with a small helper.  Unfortunately,
syncdb and the like don't have a way of detecting this dynamic model and
creating tables and such for it.  However, I've already got a mechanism
in syncdb (via signals) which uses the existing management functions to
write that new dynamic model to the database, and then in runtime
everything works perfectly happy.

Unfortunately, since there's only a syncdb signal, I can't even do
things like a reset on it, and there's definitely no way currently to
get the SQL generated from my syncdb signal.  Being able to get the
CREATE and DROP statements in text as well as each individually would be
a huge boon to this type of use (and any dynamic model use in general).

Is that a more reasonable example?

Thanks,
George