> I must say I was rather disappointed lately about the limitations of > the django ORM, which doesn't let you have any control of the joins > used internally [1]. > This doesn't seem to be a problem for most users, but if you have a > complex data model, and need to do some complex joins, out-of-the-box > django may not be the best tool for the job, and anything based on > sqlAlchemy (pylons ? turbogears ?) would be a better bet. > It's a pity, because otherwise django is great, the doc is good and > the community rocks. I was very enthusiastic about the framework [2] > until I hit those limitations and had to clutter my application with > workarounds. I still think django is great for most user cases, but > assess carefully your needs as regards the ORM.
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 cheers Olivier > > [1] See > http://groups.google.fr/group/django-users/browse_thread/thread/c8da17a98e0e3d85 > [2] Well, I never got into the "not-powerful-by-design" templating > system (I'm using mako), but it's rather independent of the rest of > the framework. > > > > > > > > -- Santiago Videla www.revolucionesweb.com.ar Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que [EMAIL PROTECTED] [EMAIL PROTECTED] somos. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
