On Wed, Dec 17, 2008 at 9:30 PM, James PIC <[email protected]> wrote: > > Is it worth reporting the bug?
It isn't entirely clear what "the bug" is. All that you have given us is an error message, and a solution that you have worked out. What you haven't given us is enough detail to reproduce the problem for ourself. We don't know what your project looks like, what is contained in your apps, if there is any strange synchronization logic being triggered - all we have is an error message. A cut down project definition that can't be synchronized would be the minimum requirement before you reported this bug in a ticket. However, at a guess, I'm going to say that the problem has been caused by your choice of model names. You appear to have named one of your models something like TypedEInformationComplementaireContact. This is a pretty long class name, and it is overflowing a column somewhere that is using the class name as a starting point. Your proposed fix (increasing the size of the columns) is really just deferring the problem. No matter what maximum size we pick, someone will choose a model name that will overflow it. I would have thought a 50 character limit was plenty, but obviously I was wrong. Your solution also suffers from the problem of backwards compatibility - there is a lot of existing code out there that relies on the existing size definition. A better solution would be to come up with a name munging scheme that guaranteed to give unique permission names that will always fit into the available space. 50 characters is plenty to establish a unique name; we already perform a similar munging with the names for database constraints. Of course, the simplest solution is for you to pick shorter class names, and for us to document the limitation. This solution has the additional benefit of enforcing good programming practice. Having descriptive class names is good, but I for one wouldn't derive much joy from using an API that had class names that spanned 50% of the width of a 80 character terminal :-) Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
