Hi, The addition to the paragraph explains this well, thanks. > (Incidentally however, is it possible to use Elixir with SQL views as > well as tables? If so, that would be one workaround for these rare > cases.)
Ok, great. It is possible to use Elixir with views, although doing this creates a few issues of its own. Primarily SA sometimes deciding it wants to update the view, which doesn't work too well :-) I have 1.0.4beta1, and the quick-started project uses > sqlalchemy.orm.mapper. Is quick-start wrong, or has this changed since > the beta release? Yeah, I changed this after 1.0.4beta1. > I definitely see your point about not wanting to duplicate existing > information, but I think there's definitely a danger of the move to > SQLAlchemy meaning that there's less documentation on how to get > started than there was with SQLObject. Fair comment. Not what I'm trying to cover in this doc, but we should put this on the todo list for the 1.1 release. 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 -~----------~----~----~----~------~----~------~--~---
