Hi, >Thanks all for your replies... Chris's suggestion above I adopted, for >the reasons he gives. Only describing the model once in one place >appeals to me, hand modifying the sql tables is just another thing for >me to screw up. > > I agree entirely. One of the main reasons I like having the model defined in a file is so I can keep it under version control.
Some people take a different approach and like to have the model completely defined in the database, and to load it from the database each time the application starts. For people who take the first approach, it would be good to have more automation on updating the database to match the model. SQLAlchemy does have a migrate project, which aims to do something like Ruby on Rails' migrate. There is the beginnings of a tool that does simple changes fully automatically, ModelUpdate, which at some point I intend to do some work on. I've got a few other priorities first though. Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
