On Mon, Jun 22, 2009 at 5:30 PM, pr<crico...@gmail.com> wrote: > Yes, I know what you mean, but It's small project with one programmer. > I want to know about speed and stability in production mode above > rules of 'programming-tao' :-)
Well, there's also the fact that: 1. Using a profile means relying on documented, guaranteed-stable behavior in Django. 2. Using the add_to_class trick means relying on undocumented internals which have no stability guarantee whatsoever, and which are subject to change without warning. Seriously: there's a documented and supported method for storing additional information related to users. Please take advantage of it. (and, really I speak from experience regarding other ways to do this; I have hacked up Django in just about every way possible, and I remember back when you could do things like outright replace models with your own definitions, and all of it was a freaking nightmare for maintainability) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
