summaryrefslogtreecommitdiff
path: root/test/orm/inheritance/polymorph.py
Commit message (Collapse)AuthorAgeFilesLines
* - unit tests have been migrated from unittest to nose.Mike Bayer2009-06-101-304/+0
| | | | | See README.unittests for information on how to run the tests. [ticket:970]
* - removed test.testing.ORMTest, test.fixtures, and allMike Bayer2009-06-021-5/+5
| | | | dependencies on those.
* - The "clear()", "save()", "update()", "save_or_update()"Mike Bayer2009-01-171-12/+12
| | | | | | Session methods have been deprecated, replaced by "expunge_all()" and "add()". "expunge_all()" has also been added to ScopedSession.
* *most* py3k warnings are resolved, with the exception of the various ↵Mike Bayer2008-12-181-1/+0
| | | | | | __setslice__ related warnings I don't really know how to get rid of
* - comparator_factory is accepted by all MapperProperty constructors. ↵Mike Bayer2008-11-241-1/+1
| | | | | | | | | | | | [ticket:1149] - added other unit tests as per [ticket:1149] - rewrote most of the "joined table inheritance" documentation section, removed badly out of date "polymorphic_fetch" and "select_table" arguments. - "select_table" raises a deprecation warning. converted unit tests to not use it. - removed all references to "ORDER BY table.oid" from mapping docs. - renamed PropertyLoader to RelationProperty. Old symbol remains. - renamed ColumnProperty.ColumnComparator to ColumnProperty.Comparator. Old symbol remains.
* - fixed endless loop bug which could occurMike Bayer2008-08-041-0/+3
| | | | | | | | | | | | within a mapper's deferred load of inherited attributes. - declarative initialization of Columns adjusted so that non-renamed columns initialize in the same way as a non declarative mapper. This allows an inheriting mapper to set up its same-named "id" columns in particular such that the parent "id" column is favored over the child column, reducing database round trips when this value is requested.
* r4695 merged to trunk; trunk now becomes 0.5.Mike Bayer2008-05-091-66/+50
| | | | 0.4 development continues at /sqlalchemy/branches/rel_0_4
* - merged with_polymorphic branch, which was merged with query_columns branchMike Bayer2008-03-291-118/+65
| | | | | | | | | | | | | | | | | - removes everything to do with select_table, which remains as a keyword argument synonymous with with_polymorphic=('*', select_table). - all "polymorphic" selectables find their way to Query by way of _set_select_from() now, so that all joins/aliasing/eager loads/etc. is handled consistently. Mapper has methods for producing polymorphic selectables so that Query and eagerloaders alike can get to them. - row aliasing simplified, so that they don't need to nest. they only need the source selectable and adapt to whatever incoming columns they get. - Query is more egalitarian about mappers/columns now. Still has a strong sense of "entity zero", but also introduces new unpublished/experimental _values() method which sets up a columns-only query. - Query.order_by() and Query.group_by() take *args now (also still take a list, will likely deprecate in 0.5). May want to do this for select() as well. - the existing "check for False discriminiator" "fix" was not working completely, added coverage - orphan detection was broken when the target object was a subclass of the mapper with the orphaned relation, fixed that too.
* - state.commit() and state.commit_all() now reconcile the current dict ↵Mike Bayer2008-03-011-13/+18
| | | | | | | | | | | | | | | | against expired_attributes and unset the expired flag for those attributes. This is partially so that attributes are not needlessly marked as expired after a two-phase inheritance load. - fixed bug which was introduced in 0.4.3, whereby loading an already-persistent instance mapped with joined table inheritance would trigger a useless "secondary" load from its joined table, when using the default "select" polymorphic_fetch. This was due to attributes being marked as expired during its first load and not getting unmarked from the previous "secondary" load. Attributes are now unexpired based on presence in __dict__ after any load or commit operation succeeds.
* - Restored 2.3 compat. in lib/sqlalchemyJason Kirtland2008-01-191-7/+7
| | | | | | | - Part one of test suite fixes to run on 2.3 Lots of failures still around sets; sets.Set differs from __builtin__.set particularly in the binops. We depend on set extensively now and may need to provide a corrected sets.Set subclass on 2.3.
* added more (failing) tests to query, will need to fix [ticket:932] [ticket:933]Mike Bayer2008-01-141-1/+0
|
* - testbase is gone, replaced by testenvJason Kirtland2008-01-121-6/+6
| | | | | | - Importing testenv has no side effects- explicit functions provide similar behavior to the old immediate behavior of testbase - testing.db has the configured db - Fixed up the perf/* scripts
* test suite deprecation rampageJason Kirtland2008-01-091-46/+52
|
* filter() criterion takes mapper equivalent_columns into account when it ↵Mike Bayer2007-12-311-0/+4
| | | | adapts to select_table. more to come in [ticket:917] .
* add a polymorphic get() testMike Bayer2007-11-191-0/+7
|
* - mapper compilation has been reorganized such that most compilationMike Bayer2007-09-021-1/+1
| | | | | | | | | | occurs upon mapper construction. this allows us to have fewer calls to mapper.compile() and also to allow class-based properties to force a compilation (i.e. User.addresses == 7 will compile all mappers; this is [ticket:758]). The only caveat here is that an inheriting mapper now looks for its inherited mapper upon construction; so mappers within inheritance relationships need to be constructed in inheritance order (which should be the normal case anyway).
* - fix for [ticket:712], more unit testsMike Bayer2007-08-041-7/+21
|
* merging 0.4 branch to trunk. see CHANGES for details. 0.3 moves to ↵Mike Bayer2007-07-271-0/+336
maintenance branch in branches/rel_0_3.
View Lorry Controller Status