Re: [Django] #14108: update loaddata to load fixtures in multi db environment for testing

[Django]

#14108: update loaddata to load fixtures in multi db environment for testing
+---
  Reporter:  berto  | Owner:  nobody 
Status:  closed | Milestone: 
 Component:  Uncategorized  |   Version:  SVN
Resolution:  duplicate  |  Keywords:  fixtures loaddata tests
 Stage:  Unreviewed | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => duplicate
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Duplicate of #14068

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #14108: update loaddata to load fixtures in multi db environment for testing

[Django]

#14108: update loaddata to load fixtures in multi db environment for testing
-+--
 Reporter:  berto|   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Uncategorized| Version:  SVN   
 Keywords:  fixtures loaddata tests  |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 I'm using django in a legacy multi database environment, where there are
 three distinct databases: default, transactions, reports.  Note, these are
 unique databases, not mirrors of each other.  When writing tests I needed
 the ability to load test data into these distinct databases.

 The current multi_db fixture setup expects all databases to load a
 particular fixture.  This patch allows the TestCase setting
 "multi_db=True" to try loading a fixture into each database rather than
 failing when data does not insert into one of the databases.

 The patch is a bit incomplete.  I'm not sure how to go about raising an
 exception if a particular fixture does not insert data into any database.
 Any thoughts would be great.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.