summaryrefslogtreecommitdiff
path: root/test/ext
Commit message (Collapse)AuthorAgeFilesLines
...
* - [bug] Fixed regression from 0.7.4 wherebyMike Bayer2012-01-281-1/+18
| | | | | | using an already instrumented column from a superclass as "polymorphic_on" failed to resolve the underlying Column. [ticket:2345]
* - [bug] implemented standard "can't set attribute" /Mike Bayer2012-01-271-6/+26
| | | | | | "can't delete attribute" AttributeError when setattr/delattr used on a hybrid that doesn't define fset or fdel. [ticket:2353]
* - [feature] Added "class_registry" argument toMike Bayer2011-12-281-0/+17
| | | | | declarative_base(). Allows two or more declarative bases to share the same registry of class names.
* - [bug] Fixed bug whereby hybrid_property didn'tMike Bayer2011-12-111-1/+46
| | | | work as a kw arg in any(), has().
* - [bug] the @compiles decorator raises anMike Bayer2011-12-061-0/+17
| | | | | | informative error message when no "default" compilation handler is present, rather than KeyError.
* - [bug] __table_args__ can now be passed asMike Bayer2011-12-041-0/+14
| | | | | | an empty tuple as well as an empty dict. [ticket:2339]. Thanks to Fayaz Yusuf Khan for the patch.
* - [bug] Fixed bug whereby column_property() createdMike Bayer2011-12-031-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | against ORM-level column could be treated as a distinct entity when producing certain kinds of joined-inh joins. [ticket:2316] - [bug] related to [ticket:2316], made some adjustments to the change from [ticket:2261] regarding the "from" list on a select(). The _froms collection is no longer memoized, as this simplifies various use cases and removes the need for a "warning" if a column is attached to a table after it was already used in an expression - the select() construct will now always produce the correct expression. There's probably no real-world performance hit here; select() objects are almost always made ad-hoc, and systems that wish to optimize the re-use of a select() would be using the "compiled_cache" feature. A hit which would occur when calling select.bind has been reduced, but the vast majority of users shouldn't be using "bound metadata" anyway :).
* - [bug] Fixed bug whereby a subclass of a subclassMike Bayer2011-10-281-13/+58
| | | | | | | | | | | | | | using concrete inheritance in conjunction with the new ConcreteBase or AbstractConcreteBase would fail to apply the subclasses deeper than one level to the "polymorphic loader" of each base [ticket:2312] - [bug] Fixed bug whereby a subclass of a subclass using the new AbstractConcreteBase would fail to acquire the correct "base_mapper" attribute when the "base" mapper was generated, thereby causing failures later on. [ticket:2312]
* - [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.
* fix this for oracleMike Bayer2011-10-151-5/+10
|
* warn when a subclass' base uses @declared_attr for a regular column -Mike Bayer2011-09-261-0/+21
| | | | does not propagate to subclasses. [ticket:2283]
* - Changed the update() method on association proxyMike Bayer2011-09-141-2/+62
| | | | | | | | dictionary to use a duck typing approach, i.e. checks for "keys", to discern between update({}) and update((a, b)). Previously, passing a dictionary that had tuples as keys would be misinterpreted as a sequence. [ticket:2275]
* - New event hook, MapperEvents.after_configured().Mike Bayer2011-09-101-34/+82
| | | | | | | | | | | | | | | | | | | | | | | | Called after a configure() step has completed and mappers were in fact affected. Theoretically this event is called once per application, unless new mappings are constructed after existing ones have been used already. - New declarative features: - __declare_last__() method, establishes an event listener for the class method that will be called when mappers are completed with the final "configure" step. - __abstract__ flag. The class will not be mapped at all when this flag is present on the class. - New helper classes ConcreteBase, AbstractConcreteBase. Allow concrete mappings using declarative which automatically set up the "polymorphic_union" when the "configure" mapper step is invoked. - The mapper itself has semi-private methods that allow the "with_polymorphic" selectable to be assigned to the mapper after it has already been configured. [ticket:2239]
* - Fixed bug whereby if __eq__() wasMike Bayer2011-09-091-0/+6
| | | | | | redefined, a relationship many-to-one lazyload would hit the __eq__() and fail. [ticket:2260] Does not apply to 0.6.9.
* - rewrite the docs for association proxy using declarative, add new ↵Mike Bayer2011-08-051-2/+29
| | | | | | | | examples, querying, etc., part of [ticket:2246] - add some accessors to AssociationProxy for attributes, test in join(), [ticket:2236] - update relationship docs to talk about callables, part of [ticket:2246]
* - Added an informative error message whenMike Bayer2011-07-211-0/+35
| | | | | | | | | ForeignKeyConstraint refers to a column name in the parent that is not found. Also in 0.6.9. - add tests for [ticket:2226], as if we hit each @declared_attr directly with obj.__get__(obj, name) instead of using getattr(cls, name). Basic inheritance mechanics are improperly used in this case, so 2226 is invalid.
* - 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.
* - Fixed declarative bug where a class inheritingMike Bayer2011-06-141-3/+16
| | | | | | from a superclass of the same name would fail due to an unnecessary lookup of the name in the _decl_class_registry. [ticket:2194]
* - 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]
* - hardcore force every connection into a strong-referenced set, rollback on ↵Mike Bayer2011-04-251-4/+5
| | | | | | | | | every test, close on every context. this uses pool events but bypasses the pool's fairy/record/dispose services. pypy still seems to expose some holes in that at least as far as what some (or maybe just one, cant find it yet) of the tests does. haven't tested this too deeply, just on sqlite + postgres, cypthon 2.7 + pypy. will see what the buildbot says
* Exclude serializer test on pypy. Problem in pickle.Michael Trier2011-04-241-0/+2
|
* - add some function examples, [ticket:2107]Mike Bayer2011-04-021-1/+34
| | | | | | - have "packagenames" be present on FunctionElement by default so that compiler.visit_function() can be called - add a test for that
* - do a close() here so that objects are guaranteed loaded newMike Bayer2011-03-271-0/+1
|
* - move all the comments that got shoved below the fixture grabs back upMike Bayer2011-03-272-0/+5
|
* - remove test.sql._base, test.engine._base, test.orm._base, move those ↵Mike Bayer2011-03-279-109/+110
| | | | | | | classes to a new test.lib.fixtures module - move testing.TestBase to test.lib.fixtures - massive search and replace
* - move all the setup_classes(cls) and setup_mappers(cls) to use aMike Bayer2011-03-271-4/+4
| | | | | local cls.Basic, cls.Comparable base class so that there is no ambiguity or hash identity behaviors getting in the way of class registration.
* - remove @testing.resolve_artifact_names, replace with direct attributeMike Bayer2011-03-262-25/+56
| | | | | | | 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
* this test fails on PyPy because it checks for a lastrowid after the ↵Alex Gaynor2011-03-161-3/+3
| | | | connection is lcosed
* Fix 3 errors in py32, from patch from lsblakk. There are still 8 failures. ↵Taavi Burns2011-03-161-3/+5
| | | | See #2088.
* Pulling 32d2b5d1962961b4134463becdd988888f797e90 onto default from rel_0_6Taavi Burns2011-03-151-1/+1
|
* - Arguments in __mapper_args__ that aren't "hashable"Mike Bayer2011-03-141-0/+21
| | | | | aren't mistaken for always-hashable, possibly-column arguments. [ticket:2091]
* - the dictionary at the end of the __table_args__Mike Bayer2011-02-171-9/+7
| | | | tuple is now optional. [ticket:1468]
* add a close to this as PG appears to be hangingMike Bayer2011-02-141-0/+1
|
* - Fixed regression whereby composite() withMike Bayer2011-02-141-1/+62
| | | | | | | | Column objects placed inline would fail to initialize. The Column objects can now be inline with the composite() or external and pulled in via name or object ref. [ticket:2058]
* - Association proxy now has correct behavior forMike Bayer2011-02-131-48/+117
| | | | | | | any(), has(), and contains() when proxying a many-to-one scalar attribute to a one-to-many collection (i.e. the reverse of the 'typical' association proxy use case) [ticket:2054]
* - Added an explicit check for the case that the nameMike Bayer2011-02-121-0/+21
| | | | | 'metadata' is used for a column attribute on a declarative class. [ticket:2050]
* make it more explicit in tests which dialect we want to use for thingsMike Bayer2011-02-112-0/+6
|
* - The compiler extension now supports overriding the defaultMike Bayer2011-02-091-32/+67
| | | | | | | compilation of expression._BindParamClause including that the auto-generated binds within the VALUES/SET clause of an insert()/update() statement will also use the new compilation rules. [ticket:2042]
* - Fixed bug where "middle" class in a polymorphic hierarchyMike Bayer2011-02-021-1/+2
| | | | | | | would have no 'polymorphic_on' column if it didn't also specify a 'polymorphic_identity', leading to strange errors upon refresh, wrong class loaded when querying from that target. [ticket:2038]
* - Horizontal shard query places 'shard_id' inMike Bayer2011-01-231-10/+32
| | | | | context.attributes where it's accessible by the "load()" event. [ticket:2031]
* - tests for hybridMike Bayer2011-01-171-100/+238
| | | | | - documentation for hybrid - rewrite descriptor, synonym, comparable_property documentation
* - 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-027-160/+158
|
* - 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.
View Lorry Controller Status