On 11/23/07, Patryk Zawadzki <[EMAIL PROTECTED]> wrote:
>
> 2007/11/23, Rudolph <[EMAIL PROTECTED]>:
> >
> > Structured markup can only represent tree like organised objects
> > (without tricks). Maybe we can keep the primary keys inside the
> > fixtures, but add an optional attribute that
2007/11/23, Rudolph <[EMAIL PROTECTED]>:
>
> Structured markup can only represent tree like organised objects
> (without tricks). Maybe we can keep the primary keys inside the
> fixtures, but add an optional attribute that indicates that the
> primary key for this object is only used to link the
Structured markup can only represent tree like organised objects
(without tricks). Maybe we can keep the primary keys inside the
fixtures, but add an optional attribute that indicates that the
primary key for this object is only used to link the objects together
when importing the data?
2007/11/23, Russell Keith-Magee <[EMAIL PROTECTED]>:
>
> On 11/23/07, Rudolph <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > My suggestion:
> > It would be nice to use the django-admin.py with an extra option to
> > dump certain data without primary keys. If you like the idea, I'll
> > file a
On 11/23/07, Rudolph <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> My suggestion:
> It would be nice to use the django-admin.py with an extra option to
> dump certain data without primary keys. If you like the idea, I'll
> file a ticket (and maybe implement it at the upcoming Django sprint).
You're not
Hi,
Sometimes fixtures without a pk come in handy because the object in
the fixture is important to the application, but it doesn't matter
which pk is has (and other objects might have been inserted by other
applications, so it's unknown which pk is available). I got the JSON
format working
