This works for me. :-)
As for you point 1), if there is no tg_init_database, then the behaviour
is exactly as before and SQLObject users will not be confused. That is
to say, I have to do an explicit act to get the new behaviour and so I
will know what will happen.
As for point 2), I am
Krys Wilken wrote:
I think both ideas are of value. An exec command for running scripts,
and a special module-level function in model.py that is run
automatically by sql create.
I might like it, too. What do you think of this:
Index: turbogears/quickstart/projectname/model.py.source
On 10/3/05, Ian Bicking [EMAIL PROTECTED] wrote:
I've actually meant to include this functionality in sqlobject-admin, if
you are interested in making the change there.
That would be excellent. The last time I used sqlobject (0.6.1) I had
to do some evil hacking to emulate both this
Hi,
I did a similar script, but I use trickiness and imports to get the
context. :-)
I like you way better, so I vote +1 for this idea.
Krys
xtian wrote:
I've been playing around with my data model, making changes to the
structure, dropping and recreating tables, and I've found it handy to
On 10/1/05, xtian [EMAIL PROTECTED] wrote:
I've been playing around with my data model, making changes to the
structure, dropping and recreating tables, and I've found it handy to
be able to run an initial data script in the context of the model
classes.
Something like:
turbogears-admin
5 matches
Mail list logo
