On 4/19/07, Tim Chase <[EMAIL PROTECTED]> wrote: ... >(with several hundred clients, drilldown > would be nice).
Indeed. I think you may want to look a the newforms-admin branch. I think the most natural would be to add auto-complete filters and multiple applied filters. Also, perhaps data_hierarchy will help in the short term: http://www.djangoproject.com/documentation/model-api/#date-hierarchy > -be careful with tracebacks if, for some reason, you have a > query-set that brings back bajillions of records and you error ... Yeah, I don't really know what to do with this. It's hard to know how big something is (memory-wise) in python, and the debugging handlers is necessarily generic. > -the default admin tool is good for blogs, bad for bajillions of > records. This might be mitigated a bit with some judicious use > of limit_choices_to but I haven't mastered such yet raw_id_admin is your friend. Again, I'd like to do an auto-complete widget here some day... > -PostgreSQL can do dumb things with your queries, which a little > jiggering/subclassing of the query object can mung into something > a little smarter (and much faster-running) Hmm. Can you give some examples? Are you saying the query planner is missing indexes or...? I haven't had this problem yet, but I bet it sucks. :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
