Use the correct database for fetching app upgrade info.

Review Request #10579 — Created June 5, 2019 and submitted

Information

Django Evolution
master

Reviewers

We had a couple calls that used the default database, breaking
operations when testing against multiple databases. This involved calls
to get_app_upgrade_info() in signature deserialization (which didn't
know about databases) and the saving of Version and Evolution
models.

This updates all signature deserialization to support specifying a
database, and updates the model saving to use the evolver's assigned
database.

Unit tests pass on all supported versions of Django.

Summary ID
Use the correct database for fetching app upgrade info.
We had a couple calls that used the default database, breaking operations when testing against multiple databases. This involved calls to `get_app_upgrade_info()` in signature deserialization (which didn't know about databases) and the saving of `Version` and `Evolution` models. This updates all signature deserialization to support specifying a database, and updates the model saving to use the evolver's assigned database.
c7aa87dd440c66ed7fbd3c8aef454bfb650f4047
david
  1. Ship It!
  2. 
      
chipx86
Review request changed
Status:
Completed
Change Summary:
Pushed to master (664fdef)