Re: multi natural_key dependencies problem

i've removed it. thx. On Mar 16, 11:38 am, Karen Tracey wrote: > Please don't crosspost to both django-users and django-developers. Pick the > right list and post once. This sounds like a usage question, so it belongs > on django-users. > > Karen -- You received this

Re: multi natural_key dependencies problem

Please don't crosspost to both django-users and django-developers. Pick the right list and post once. This sounds like a usage question, so it belongs on django-users. Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this

multi natural_key dependencies problem

how to set multi natural_key dependincies? Model code as following: class Menu(models.Model): mName = models.CharField(max_length=256) mTitle = models.CharField(max_length=256) url = models.CharField(max_length=1024, blank=True, null=True) ordering = models.IntegerField()

Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

There is a ticket for something similar #8896 (http://code.djangoproject.com/ticket/8896). Let urlresolvers also route according to hostname. -- Gert Mobile: +32 498725202 Web: http://gert.selentic.net 2010/3/15 jens : > On Mar 15, 3:44 pm, Yuri Baburov

Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

On Mar 15, 3:44 pm, Yuri Baburov wrote: > How do you like the following idea: > startproject command puts a fixture for django.contrib.sites (and > fixture for superuser probably) to the root folder or whatever, to be > loaded with syncdb? IMHO it would be a great, if django

Re: [Proposal] Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

Hello all, How do you like the following idea: startproject command puts a fixture for django.contrib.sites (and fixture for superuser probably) to the root folder or whatever, to be loaded with syncdb? That way also encourage users to get more familiar with fixtures. Of course it's too far for

Re: [Proposal] Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

Le 14 mars 2010 à 12:27, James Bennett a écrit : > On Fri, Mar 12, 2010 at 4:39 PM, aditya wrote: > >> Currently, Django uses "example.com" for both the domain and the >> name. The only way to change that is to wade into the actual >> database. > 2. If it turns out