Re: ContentTypes and fixtures

2009-01-30 Thread Eric Holscher
On Jan 30, 12:06 pm, Oliver Beattie wrote: > > Oliver, meet ticket #7052. Ticket #7052, meet Oliver :-)\ > > Thanking you, I'm not as familiar with the tickets as I should be =) > > > The best workaround that I can suggest is to include your ContentTypes > > in your fixtures. They are dumpable

Re: ContentTypes and fixtures

2009-01-30 Thread Oliver Beattie
> Oliver, meet ticket #7052. Ticket #7052, meet Oliver :-)\ Thanking you, I'm not as familiar with the tickets as I should be =) > The best workaround that I can suggest is to include your ContentTypes > in your fixtures. They are dumpable objects, just like everything else > in Django. If your f

Re: ContentTypes and fixtures

2009-01-29 Thread felix
this has bitten me too recently. in general I'm moving away from fixtures. they are breakable, they suffer when the codebase is refactored. particularily for tests I no longer use fixtures. I would suggest trying the dump-to–python-code method ideally there should be a away to dump a group (

Re: ContentTypes and fixtures

2009-01-28 Thread Russell Keith-Magee
On Thu, Jan 29, 2009 at 7:36 AM, Oliver Beattie wrote: > > How can I be sure that the ContentType IDs are always constant, and > therefore my data in fixtures is guaranteed to always point to the > right object? Oliver, meet ticket #7052. Ticket #7052, meet Oliver :-) This is an annoying bug th

ContentTypes and fixtures

2009-01-28 Thread Oliver Beattie
Hey everyone, I'm converting some of my stuff over to use Django fixtures instead of the old dump-import a SQL file. This is all going very well, until I realised that my GenericForeignKeys might be broken if I rely on fixtures. In my old SQL method, this was not an issue as I could guarantee th