Hi Russ,
I opened #14068.
I can not think of an easy fix as those I would choose will have side effects
on other multi database settings.
If the core team can come with a design decision on the fix, I'll be happy to
implement it.
Regards,
Xavier.
Le 5 août 2010 à 13:31, Russell Keith-Magee a é
On Thu, Aug 5, 2010 at 3:44 PM, Xavier Ordoquy wrote:
> Hi Russ,
>
> Indeed, my investigations have lead me to #14025 which fixed the major issue.
>
> If I remember correctly the corrupted file part was due to the fact that I
> was still using an "old style" fixture filename - ie .json instead of
Hi Russ,
Indeed, my investigations have lead me to #14025 which fixed the major issue.
If I remember correctly the corrupted file part was due to the fact that I was
still using an "old style" fixture filename - ie .json instead of
..json with data on both databases.
If you find it useful, I ca
On Thu, Jul 29, 2010 at 6:02 PM, Xavier Ordoquy wrote:
> Hi there.
>
> I'm currently working on a project where I use a legacy database with a
> django one.
> I've setup the multi database support and it seems to work pretty well.
> However, I'm getting an issue with testing.
>
> I need a fixture
4 matches
Mail list logo
