Hmmm.. not sure that argument makes much sense. In this case, it sounds like the deep integration is part of the problem here. If you can't swap out the orm without losing functionality than that would seem like a significant disadvantage. In this case Turbogears would likely be better solution as it is not limited in this manner(and also has a vibrant and active community)
On Sep 26, 1:02 pm, olivier <[EMAIL PROTECTED]> wrote: > > Thank you very much, you just save a lot of work. > > > I will take a look to TurboGears. > > > BTW, I have been trying django for 2 days and it's very nice, may be for > > other project > > I'm not sure you should make a decision that fast ;o) > I don't know where pylons and TG are heading now (integration, > stability, doc, community, ...) and how much you researched on those > frameworks, but django's deep integration is a serious advantage worth > considering. > If I were you, I would design the model and try to run the most > complicated queries with django's ORM. > If you reach django's limitations, or feel you're on the edge, it's > probably just one hour of find/replace in your favorite editor to get > the (basic) sqlAlchemy's equivalent. > > Cheers, > > Olivier --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
