Thanks for the replies, both.
> This idea has occurred to me before, and I can see how it could be
> useful, but I got caught up on one significant detail: how do you
> handle references? When you specify the PK, you provide an identifier
> to use as a cross reference. If this identifier no
On 9/7/07, Nathaniel Whiteinge <[EMAIL PROTECTED]> wrote:
>
> Can fixtures have auto-incrementing primary keys or must you have
> specific PKs in the the serialized json/xml/etc files? If not, is
> there a reason for this?
This idea has occurred to me before, and I can see how it could be
On Sep 6, 10:55 pm, Nathaniel Whiteinge <[EMAIL PROTECTED]> wrote:
> Can fixtures have auto-incrementing primary keys or must you have
> specific PKs in the the serialized json/xml/etc files? If not, is
> there a reason for this?
>
> I'm programmatically generating fixtures from Freebase.org
Can fixtures have auto-incrementing primary keys or must you have
specific PKs in the the serialized json/xml/etc files? If not, is
there a reason for this?
I'm programmatically generating fixtures from Freebase.org queries for
a project. Although it's not a much extra work to add a pk counter,
4 matches
Mail list logo
