Hi Valentin, On 04/27/2011 10:33 PM, Valentin Golev wrote: > 1. I've run into something that seems like a bug. If it really is a bug, > I'll file a ticket, if it's not, please clarify the behaviour, and, in > this case, I think a better error message will be awesome. > > Basically, if there are two permissions for a model with same codenames > and different descriptions, Django tries to add both in the database, > but there is a unique index on codename so it all crashes horribly.
This sounds like a bug to me - Django should detect the duplicate codename and give a reasonable error before trying to save it to the database. Please do file a bug (if there isn't one already). > 2. Another idea being in my head lately is that since there is a better > logging support in django nowadays, maybe it's time to try adding a > dozen of warnings and suggestions to humble Django users. I'd like to > try to improve overall error-reporting and in Django. Several ideas from > the top of my head: > > * Handling apps with no "models.py". It seems like Django silences this > error and removes the app from the app list. It doesn't play nice with > several things, like testing. I think there should be a warning in > runserver's console. I agree that we could do something better here. The first thing I'd want to check is how this is handled in the app-loading branch that Jannis Leidel and Arthur Koziel are currently working on, from Arthur's GSoC work last summer. That will hopefully be merged soon, and will change a fair bit of behavior around model-loading and INSTALLED_APPS. > * I think there should be ready to use runserver-console handler for > logging (seems like just a normal StreamHandler), and it could be > enabled by default in settings.py This sounds to me worth filing a ticket for, if there isn't one already. I'm not sure about enabling it by default, but perhaps with a flag to runserver. > * I also think there should be some interesting logging namespaces, like > django.db.query for logging all queries. My understanding is that there's a general intention to do more useful logging now that the logging framework is in place, so I think specific tickets and patches in this area would be welcome. > * An awesome feature will be helping with solving O(n) queries errors > (and other database mistakes) - gentle warnings in console when two > almost same queries are running during the same request. It doesn't seem > like a simple task to do, but definitely like an interesting one. My immediate reaction is that we don't need to get this tricky; just making it easier to log queries and see that log in console will greatly improve immediate awareness of O(n) query situations. Carl -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
