On 12/18/06, Jeffrey Zelt <[EMAIL PROTECTED]> wrote: ... > 3. My only serious request involves the DB API. The Django ORM is > simply too limiting. I was not able to do what I wanted without jumping > through hoops. I was forced to use the: > > extra( where=..., params=..., tables=...) > > QuerySet method often, and found that when this method is combined with > the other QuerySet methods (filter, exclude, ...) the combined SQL query > generated by Django often did not do what was expected.
Oh? Please provide a set of failing tests to demonstrate the expected behavior and failings. ... > I realize that many people are probably happy with the default ORM > because not all applications have serious database requirements, but for > me it is the single most limiting feature of Django. I will not be > satisfied if the current ORM is capable of fulfilling 95% requirements > if the last 5% requires several days of additional pain (and sluggish > results). I think it's surprising and a little egotistical to assume your project had requirements far beyond what is typical. Before pushing Django's ORM along the slope, give this a read: http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Computer+Science.aspx Perhaps if you described exactly a problem you had with the QuerySet/custom SQL round-trip, we could solve a problem or suggest alternate strategies. Cheers, Jeremy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
