| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
| |
time, as it is re-initialized as a copy made for an inheriting mapper, and no longer can get to the correct inheriting table.
|
| |
|
|
|
|
|
| |
closed-minded about how it creates the join crit
erion as well as the sync rules in inheritance. syncrules have been tightened up to be smarter about creating a new
SyncRule given lists of tables and a join clause. properties also checks for relation direction against the "noninherited table" which for the moment makes it a stronger requirement that a relation to a mapper must relate to that mapper's main table, not any tables that it inherits from.
|
| | |
|
| |
|
|
| |
more to be *feared* ! :)
|
| | |
|
| | |
|
| |
|
|
| |
one row returned, courtesy J.Ellis
|
| |
|
|
| |
"parent"/"mapper" table to be more constrained. this change was originally in [changeset:1101] to help out the polymorph example but it now works without it. the change breaks the Post/Comment relationship in the ZBlog demo since the Post mapper has the comments table inside of it (also with no workaround).
|
| |
|
|
|
|
|
|
|
|
|
| |
more intelligent bind parameter dictionary that does type conversions late and preserves the unconverted value; used to fix mappers not comparing correct value in post-fetch [ticket:110]
removed pre_exec assertion from oracle/firebird regarding "check for sequence/primary key value"
fix to Unicode type to check for null, fixes [ticket:109]
create_engine() now uses genericized parameters; host/hostname, db/dbname/database, password/passwd, etc. for all engine connections
fix to select([func(column)]) so that it creates a FROM clause to the column's table, fixes [ticket:111]
doc updates for column defaults, indexes, connection pooling, engine params
unit tests for the above bugfixes
|
| | |
|
| |
|
|
|
|
|
|
| |
the case of
inheritance. relations now create priamry/secondary joins against that lead table. if you want to create it against
an inherited table, use explicit join conditions.
added 'correlate' argument to CompoundSelect to get polymorph example working again.
|
| | |
|
| |
|
|
| |
the primaryjoin and secondaryjoin, and raises a descriptive exception if so.
|
| |
|
|
| |
mapper, when the inheritance/eager loads share the same table. mapper inheritance will also favor the columns from the child table over those of the parent table when assigning column values to object attributes. "correlated subqueries" require a flag "correlated=True" if they are in the FROM clause of another SELECT statement, and they want to be correlated. this flag is set by default when using an "exists" clause.
|
| | |
|
| | |
|
| |
|
|
| |
send keyword arguments that will be placed on the relation
|
| |
|
|
|
|
| |
tests as a unit test eagerload2.
got eagerload1 to be a unit test also.
|
| |
|
|
| |
mapper; even though this is not usually needed, it allows certain exotic combinations of mapper setups to work (i.e. the one in the polymorph example)
|
| |
|
|
|
| |
fixes to relation to enable it to locate "direction" more consistently with inheritance relationships
more tweaks to parenthesizing subqueries, unions, etc.
|
| | |
|
| |
|
|
| |
properly receives defaults on inserts)...
|
| |
|
|
| |
attributes, util
|
| |
|
|
| |
confuses users
|
| | |
|
| |
|
|
|
|
| |
phase of a one-to-many post update
closes [ticket:67]
|
| | |
|
| |
|
|
|
|
| |
[ticket:81]
TableFinder becomes a list-implementing object (should probably create clauseutils or sqlutils for these little helper visitors)
|
| |
|
|
| |
to make use of it as well as properties. also clarifies the "synchronization" idea
|
| |
|
|
|
|
| |
on it, to make
room for more aggressive "identity map" assertion when modifying objects incoming from a result set
|
| |
|
|
| |
"validate" operation to cut down on method overhaed
|
| |
|
|
|
|
| |
occurs not just
at commit time but also when its logged as "dirty" or "deleted".
|
| |
|
|
| |
work even when one side of the relation has both tables in it (new unittest will be added to inheritance.py to show this...)
|
| |
|
|
|
| |
clause elements including tables and columns, schema package deals with "physical"
representations
|
| |
|
|
| |
get the full list of primary key cols
|
| |
|
|
| |
properties without getting a "list changed during iteration" error
|
| |
|
|
|
|
| |
so check for this
during delete
|
| | |
|
| |
|
|
| |
getting messed up by late add_property() calls
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this includes:
sql.Alias object keeps track of the immediate thing it aliased as well
as the ultimate non-aliased (usually a Table) object, so that proxied columns can have
a "parent" attribute
some cleanup to SelectBaseMixin.order_by_clause to allow easier access, needs more cleanup
engine has been making two ResultProxies all this time, added "return_raw" quickie flag to
disable that
some cleanup to _get_col_by_original so that it also works for oid columns, new eager load stuff
more aggressively aliaseses orderby's so this was needed
EagerLoader now makes "chains" of unique aliased eager loaders in all cases. no need for
use_alias/selectalias anymore since it aliases every time.
properly detects recursive eager loads and terminates them with a lazyloader, instead of
raising an exception. totally simplified setup() and init() is more straightforward and has
a single codepath now instead of two or three.
|
| |
|
|
|
| |
version has "property" accessor which returns MapperProperty at
the class level
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
compile_synchronizers in PropertyLoader needed to take into account the full list of tables for each mapper when looking for synchronization rules, not just primary table
|
| | |
|
| | |
|