Re: help with fixtures

On Mon, Jun 16, 2008 at 2:43 PM, Gene Campbell <[EMAIL PROTECTED]> wrote: > > Many thanks for a very helpful response!! > > At this point, I assume the proper practice is to create the users in > a setup() method when unittesting instead of assuming they'll be > brought up automatically when testi

Re: help with fixtures

Many thanks for a very helpful response!! At this point, I assume the proper practice is to create the users in a setup() method when unittesting instead of assuming they'll be brought up automatically when testing. (Sorry, it's been a long day - I hope that makes sense.) On Mon, Jun 16, 2008

Re: help with fixtures

On Mon, Jun 16, 2008 at 11:36 AM, ristretto <[EMAIL PROTECTED]> wrote: > > I'm running into this too. Can someone confirm this related to MySQL > InnoDB tables or not? This is unrelated to MySQL or InnoDB (although that configuration will cause some difficulties with fixtures that have circular

Re: help with fixtures

Hi Alex, I had the same problem and it almost drove me crazy. I even changed from MySQL to PostgreSQL to rule out the MySQL-DB constraints issue. But the solution was far more simple: the command 'syncdb' already populates some tables, e.g. django_content_types and loaddata therefore tries to up

Re: help with fixtures

On 8/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Then, I am have exported data in all various formats, with hope that > one of them would work: > > ./manage.py dumpdata --format=python > data.python Python fixtures aren't really intended for use by end users - its an internal format t

Re: help with fixtures

Hi Alex, might be worth including the data.json output for people to take a look at. -Michael On Aug 24, 5:15 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I have quite complex application and want to make test suite for it. > Since its complex, I need some data being populated first, so