summaryrefslogtreecommitdiff
path: root/test/ext/test_mutable.py
Commit message (Collapse)AuthorAgeFilesLines
...
* - [bug] Fixed bug where unpickled object didn'tMike Bayer2012-01-281-5/+27
| | | | | | | | have enough of its state set up to work correctly within the unpickle() event established by the mutable object extension, if the object needed ORM attribute access within __eq__() or similar. [ticket:2362]
* - [bug] the value of a composite attribute is nowMike Bayer2011-10-261-7/+36
| | | | | | | | | | | | | | | | | expired after an insert or update operation, instead of regenerated in place. This ensures that a column value which is expired within a flush will be loaded first, before the composite is regenerated using that value. [ticket:2309] - [bug] The fix in [ticket:2309] also emits the "refresh" event when the composite value is loaded on access, even if all column values were already present, as is appropriate. This fixes the "mutable" extension which relies upon the "load" event to ensure the _parents dictionary is up to date, fixes [ticket:2308]. Thanks to Scott Torborg for the test case here.
* - Fixed bug in the mutable extension wherebyMike Bayer2011-07-011-0/+18
| | | | | | | if None or a non-corresponding type were set, an error would be raised. None is now accepted which assigns None to all attributes, illegal values raise ValueError.
* - Fixed bug in the mutable extension wherebyMike Bayer2011-06-301-1/+4
| | | | | | if the same type were used twice in one mapping, the attributes beyond the first would not get instrumented.
* - Repaired new "mutable" extension to propagateMike Bayer2011-06-041-3/+107
| | | | | | events to subclasses correctly; don't create multiple event listeners for subclasses either. [ticket:2180]
* py3k test fixMike Bayer2011-05-141-2/+1
|
* - Fixed bugs in sqlalchemy.ext.mutable extension whereMike Bayer2011-05-141-1/+26
| | | | | | `None` was not appropriately handled, replacement events were not appropriately handled. [ticket:2143]
* - remove test.sql._base, test.engine._base, test.orm._base, move those ↵Mike Bayer2011-03-271-7/+7
| | | | | | | classes to a new test.lib.fixtures module - move testing.TestBase to test.lib.fixtures - massive search and replace
* - remove @testing.resolve_artifact_names, replace with direct attributeMike Bayer2011-03-261-7/+4
| | | | | | | access to the cls/self.tables/classes registries - express orm/_base.py ORMTest in terms of engine/_base.py TablesTest, factor out common steps into TablesTest, remove AltEngineTest as a separate class. will further consolidate these base classes
* - oracle fixesMike Bayer2011-01-151-5/+5
|
* - add support for pickling with mutable scalars, mutable compositesMike Bayer2011-01-021-13/+60
| | | | | | | - add pickle/unpickle events to ORM events. these are needed for the mutable extension. - finish mutable extension documentation, consolidate examples, add full descriptions
* - whitespace removal bonanzaMike Bayer2011-01-021-25/+24
|
* - add length to varcharsMike Bayer2010-12-311-2/+2
|
* - removes the "on_" prefix.Mike Bayer2010-12-301-3/+3
|
* - they don't want "on_". First step, change the naming convention on EventsMike Bayer2010-12-301-4/+4
| | | | so that non-events are just _name.
* - mutable examples now move into sqlalchemy.ext.mutableMike Bayer2010-12-291-0/+238
- streamline interfaces, get Mutable/MutableComposite to be as minimal in usage as possible - docs for mutable, warnings regrarding mapper events being global - move MutableType/mutable=True outwards, move orm tests to its own module, note in all documentation - still need more events/tests for correct pickling support of composites, mutables. in the case of composites its needed even without mutation. see [ticket:2009]