2008/6/23 ricardo soares <[EMAIL PROTECTED]> > > > 2008/6/13, ricardo soares <[EMAIL PROTECTED]>: >> >> >> >> 2008/5/28, ricardo soares <[EMAIL PROTECTED]>: >>> >>> Welcome to Casino Fantasy™ We are part of the largest, longest-running >>> and most popular group of International online casinos. Our parent company >>> started building and training our team of experienced gaming professionals >>> in 1996. Since we began serving players in early 1997, our growth has been >>> astonishing. Today, we have an established track record of great service and >>> satisfied customers. Internationally, we handle over $500,000,000 in secure >>> gaming transactions per year, delivering more than 100,000,000 games to >>> players from over 200 countries. >>> For a limited time, get up to $100 in free bonus chips added to your >>> player account! After installing the software, simply register, make a >>> deposit and we will match 100% of the amount of your fi >> which information was edited >> * uncertainty over whether other models should have user or profile >> as FK >> * uncertainty over whether friendship relationship should be on >> user >> or profile >> >> Some people have suggested that the qsrf inheritance be used to >> create >> a model derived from User, and a custom authentication backend >> written >> that creates and returns instances of the appropriate model. I'm >> fairly "meh" on that idea (and ORM-based inheritance in general, but >> that's another story), and it doesn't seem to be a solution supported >> by the official documentation. >> >> What I'd like to see is an easy, supported way of specifying the name >> of the user model in the settings file, thereby avoiding all of the >> above complexity. There are a few places where hard-coded references >> to django.contrib.auth.models.User would need to be replaced, but I >> can think of a couple of ways of doing that, including backwards- >> compatible ones. Can anyone think of any reasons why this would be a >> bad idea? I'd certainly be willing to provide a suitable patch. > >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
