Multi-db no longer supported.

[ashchristopher]

In DjangoModelFactory, the factory will eventually make a call to _setup_next_sequence regardless of whether we are building or createing. This means the strategy of building an instance, then settings it's destination via save(using='other_db') is no longer valid.

When using factory.BUILD_STRATEGY, it should not be hitting the database at all.

I can mitigate this issue by overriding the _setup_next_sequence() method.

@classmethod
def _setup_next_sequence(cls):
    return 1

[rbarrois]

Yes, that's an issue; however, I don't think the behavior you describe has ever worked in the last 3 years :/

The workaround you've described is the best solution right now.

This issue originates from a feature that says "if you're settings unique fields through factory.Sequence(), two successive script runs should hopefully provide different values"

[ashchristopher]

In the past, we were able to override the _prepare() method to take into account db routers, but since the refactor, _prepare() is called after _setup_next_sequence.

It does seem odd to me that when using the factory.BUILD_STRATEGY strategy, that we would have to hit the db.

[rbarrois]

This issue has been fixed in 13d310f, and will be part of the 2.5.0 release.