summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/ext
Commit message (Collapse)AuthorAgeFilesLines
...
* - move load_scalar_attributes out to loading.pyMike Bayer2012-07-141-18/+19
|
* - [moved] The InstrumentationManager interfaceMike Bayer2012-06-241-0/+396
| | | | | | | | | | | | | and the entire related system of alternate class implementation is now moved out to sqlalchemy.ext.instrumentation. This is a seldom used system that adds significant complexity and overhead to the mechanics of class instrumentation. The new architecture allows it to remain unused until InstrumentationManager is actually imported, at which point it is bootstrapped into the core.
* remove ambiguous languageMike Bayer2012-06-181-2/+7
|
* Add some `Sphinx` paragraph level versions informations markups,Mike Bayer2012-06-083-19/+27
| | | | such as ``.. versionadded::``, ``.. versionchanged::`` and ``.. deprecated::``.
* - [bug] Fixed bug in declarativeMike Bayer2012-05-241-6/+3
| | | | | | | | | | | | | | whereby the precedence of columns in a joined-table, composite column (typically for id) would fail to be correct if the columns contained names distinct from their attribute names. This would cause things like primaryjoin conditions made against the entity attributes to be incorrect. Related to [ticket:1892] as this was supposed to be part of that, this is [ticket:2491]. Also in 0.7.8.
* looks like I finally stepped on someone elses dunders...will have to figure outMike Bayer2012-05-201-3/+3
| | | | how to make a public API for this anyway
* - reorganize the usage of __mapper_args__ so that it's onlyMike Bayer2012-05-181-106/+142
| | | | | called after the __prepare__() step, if any, so that everything to do with the mapping occurs after the table is reflected.
* - [feature] The "deferred declarativeMike Bayer2012-05-171-8/+11
| | | | | | | | | | | | | | | | reflection" system has been moved into the declarative extension itself, using the new DeferredReflection class. This class is now tested with both single and joined table inheritance use cases. [ticket:2485] - [bug] The autoload_replace flag on Table, when False, will cause any reflected foreign key constraints which refer to already-declared columns to be skipped, assuming that the in-Python declared column will take over the task of specifying in-Python ForeignKey or ForeignKeyConstraint declarations.
* - add DeferredReflection to declarative itselfMike Bayer2012-05-171-24/+113
| | | | - split out test_declarative into four separate modules
* clean this up some more. __mapper__ isn't even set up.Mike Bayer2012-05-151-14/+11
|
* implement support for __prepare__ declarative method. this signals thatMike Bayer2012-05-151-10/+51
| | | | | | | | the mapping should not be constructed immediately; instead, the info for the mapping is placed into an interm object _MapperThingy which serves as the mapper for the purposes of figuring out inheritance, etc. Later, the prepare_deferred_mapping() function can be called given a base which will invoke __prepare__ for each mapped class.
* fix import hereMike Bayer2012-04-241-4/+4
|
* - remove sqlsoup [ticket:2262]Mike Bayer2012-04-241-813/+0
| | | | - remove sqlalchemy.exceptions [ticket:2433]
* - merged #1401 branch from bitbucketMike Bayer2012-04-221-1/+5
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - resolved some serious speed hits I missed, we need to ensure only deannotated columns are used in the local/remote collections and soforth so that hash lookups against mapped columns don't dig into __eq__() - fix some other parity mismatches regarding stuff from [ticket:2453], including finding another case where _deep_annotate() was doing the wrong thing, new tests. - [feature] Major rewrite of relationship() internals now allow join conditions which include columns pointing to themselves within composite foreign keys. A new API for very specialized primaryjoin conditions is added, allowing conditions based on SQL functions, CAST, etc. to be handled by placing the annotation functions remote() and foreign() inline within the expression when necessary. Previous recipes using the semi-private _local_remote_pairs approach can be upgraded to this new approach. [ticket:1401]
| * - move create_lazy_clause() to relationshipsMike Bayer2012-04-011-1/+5
| | | | | | | | - add foreign, remote annotations to declarative
* | - [bug] Fixed bug which would preventMike Bayer2012-04-011-0/+14
| | | | | | | | | | OrderingList from being pickleable [ticket:2454]. Courtesy Jeff Dairiki
* | typos in lib/sqlalchemy/extDiana Clarke2012-03-174-5/+5
| |
* | fix up docs a bit here, not sure if some enhancements had alreadyMike Bayer2012-03-131-30/+35
| | | | | | | | been made as things didn't seem as bad as [ticket:2306] indicated
* | - add __table_cls__ option to declarative, not publicized yet, is for the momentMike Bayer2012-03-121-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | for the benefit of the test.lib.schema package. - use test.lib.schema.Table for the table within test.lib.fixtures.DeclarativeMappedTest - [bug] Removed the check for number of rows affected when doing a multi-delete against mapped objects. If an ON DELETE CASCADE exists between two rows, we can't get an accurate rowcount from the DBAPI; this particular count is not supported on most DBAPIs in any case, MySQLdb is the notable case where it is. [ticket:2403]
* | - add OrderingList class and other functions to sphinx documentationMike Bayer2012-02-121-4/+3
|/ | | | [ticket:2391]
* declarative reflection exampleMike Bayer2012-01-281-1/+34
|
* - [bug] implemented standard "can't set attribute" /Mike Bayer2012-01-271-0/+4
| | | | | | "can't delete attribute" AttributeError when setattr/delattr used on a hybrid that doesn't define fset or fdel. [ticket:2353]
* add examples for multi metadata under __abstract__, custom vertical partitioningMike Bayer2012-01-111-0/+21
|
* sqlsoup is released separatelyMike Bayer2012-01-081-2/+9
|
* fix small update doc issue [ticket:2158]Mike Bayer2012-01-081-1/+1
|
* happy new yearMike Bayer2012-01-0410-10/+10
|
* document that strings are accepted with declarative/secondaryMike Bayer2011-12-291-0/+9
|
* - [feature] Added "class_registry" argument toMike Bayer2011-12-281-1/+12
| | | | | declarative_base(). Allows two or more declarative bases to share the same registry of class names.
* fix a whole bunch of note:: / warning:: that were inline,Mike Bayer2011-12-254-10/+24
| | | | no longer compatible with docutils 0.8
* - [bug] the @compiles decorator raises anMike Bayer2011-12-061-1/+7
| | | | | | informative error message when no "default" compilation handler is present, rather than KeyError.
* refine this a bitMike Bayer2011-12-051-4/+18
|
* - [feature] Added an example to the hybrid docsMike Bayer2011-12-051-0/+134
| | | | | | | | | of a "transformer" - a hybrid that returns a query-transforming callable in combination with a custom comparator. Uses a new method on Query called with_transformation(). The use case here is fairly experimental, but only adds one line of code to Query.
* - [bug] __table_args__ can now be passed asMike Bayer2011-12-041-9/+9
| | | | | | an empty tuple as well as an empty dict. [ticket:2339]. Thanks to Fayaz Yusuf Khan for the patch.
* - [bug] Fixed bug whereby a subclass of a subclassMike Bayer2011-10-281-11/+18
| | | | | | | | | | | | | | 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]
* plus a period. seriously. should i just watch TV today instead of ↵Mike Bayer2011-10-171-1/+1
| | | | screwing more things up
* and i screwed it upMike Bayer2011-10-171-1/+6
|
* updated conventions on mixinsMike Bayer2011-10-171-17/+26
|
* link to declarative concrete helper docrel_0_7_3Mike Bayer2011-10-161-0/+2
|
* fix typos [ticket:2294] [ticket:2300]. these are both due to reworkings of ↵Mike Bayer2011-10-151-3/+0
| | | | 0.6 docs that don't have these typos
* - SQLSoup will not be included in version 0.8Mike Bayer2011-09-261-0/+5
| | | | | | | | of SQLAlchemy; while useful, we would like to keep SQLAlchemy itself focused on one ORM usage paradigm. SQLSoup will hopefully soon be superseded by a third party project. [ticket:2262]
* warn when a subclass' base uses @declared_attr for a regular column -Mike Bayer2011-09-261-0/+6
| | | | does not propagate to subclasses. [ticket:2283]
* - Changed the update() method on association proxyMike Bayer2011-09-141-4/+13
| | | | | | | | 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]
* fix sentenceMike Bayer2011-09-101-1/+1
|
* - New event hook, MapperEvents.after_configured().Mike Bayer2011-09-101-6/+205
| | | | | | | | | | | | | | | | | | | | | | | | 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]
* document autocommit when using the compiler extension, update the ↵Mike Bayer2011-08-181-0/+49
| | | | "understanding autocommit" section
* declarify the mapper config docsMike Bayer2011-08-071-50/+2
|
* - rework tutorial to be all declarative, all the timeMike Bayer2011-08-061-11/+54
| | | | - add detail to declarative docs about base classes
* - second pass through association proxy docs, some more links on ↵Mike Bayer2011-08-061-22/+41
| | | | any()/has(), MapperProperty
* - rewrite the docs for association proxy using declarative, add new ↵Mike Bayer2011-08-051-19/+76
| | | | | | | | 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-2/+0
| | | | | | | | | 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.