On Thu, Mar 24, 2011 at 3:29 PM, Simone Dalla wrote:
>> Natural keys were introduced in 1.2. How would you do this in 1.1?
>
> 1.2
> --
You mean 1.3, right? ;o)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email
2011/3/24 Shawn Milochik
> On Thu, Mar 24, 2011 at 2:29 PM, Simone Dalla wrote:
> >
> > maybe option --natural
> >
> http://docs.djangoproject.com/en/1.3/ref/django-admin/#dumpdata-appname-appname-appname-model
> >
>
>
> Natural keys were introduced in 1.2. How would you do this in 1.1?
>
1.2
On Thu, Mar 24, 2011 at 2:29 PM, Simone Dalla wrote:
>
> maybe option --natural
> http://docs.djangoproject.com/en/1.3/ref/django-admin/#dumpdata-appname-appname-appname-model
>
Natural keys were introduced in 1.2. How would you do this in 1.1?
Or maybe there's a cleaner answer when the problem
2011/3/24 LurkingFrog
> Currently, I am writing unit tests for an application that uses
> generic foreign keys. Since the contenttypes are regenerated every
> test, I was wondering the most effective way to reconcile the existing
> test data with the new contenttypes PKs.
>
> My current thinking
Currently, I am writing unit tests for an application that uses
generic foreign keys. Since the contenttypes are regenerated every
test, I was wondering the most effective way to reconcile the existing
test data with the new contenttypes PKs.
My current thinking is to make an explicit fixture the
5 matches
Mail list logo
