summaryrefslogtreecommitdiff
path: root/tests/test_alchemy.py
Commit message (Collapse)AuthorAge
* Update header years.Raphaël Barrois2015-03-26
|
* Remove automagic pk-based sequence setupRaphaël Barrois2014-11-16
| | | | | | | | | | | | | | | | | | | | | | | | Related to issues #78, #92, #103, #111, #153, #170 The default value of all sequences is now 0; the automagic ``_setup_next_sequence`` behavior of Django/SQLAlchemy has been removed. This feature's only goal was to allow the following scenario: 1. Run a Python script that uses MyFactory.create() a couple of times (with a unique field based on the sequence counter) 2. Run the same Python script a second time Without the magical ``_setup_next_sequence``, the Sequence counter would be set to 0 at the beginning of each script run, so both runs would generate objects with the same values for the unique field ; thus conflicting and crashing. The above behavior having only a very limited use and bringing various issues (hitting the database on ``build()``, problems with non-integer or composite primary key columns, ...), it has been removed. It could still be emulated through custom ``_setup_next_sequence`` methods, or by calling ``MyFactory.reset_sequence()``.
* Rename 'target' to 'model'.Raphaël Barrois2014-05-18
|
* Switch tests to class Meta.Raphaël Barrois2014-05-18
|
* Migrate factory.alchemy to class MetaRaphaël Barrois2014-05-18
|
* Properly handle Sequence & inheritance (Closes #93).Raphaël Barrois2013-09-17
| | | | | There was also a nasty bug: with class FactoryB(FactoryA), FactoryB's sequence counter started at the value of FactoryA's counter when FactoryB was first called.
* Fix tests for sqlalchemy.Raphaël Barrois2013-06-20
| | | | Also add them to travis.
* Fixed SQLAlchemy tests on Python32minimumserious2013-06-20
|
* Added some tests for SQLAlchemyModelFactoryminimumserious2013-06-20