| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
0.4 development continues at /sqlalchemy/branches/rel_0_4
|
|
|
|
|
|
|
|
|
|
|
| |
connection to a nested session transaction.
- session.transaction now always refers to the innermost active transaction, even when commit/rollback are called directly on the session transaction object.
- when preparing a two-phase transaction fails on one connection all the connections are rolled back.
- two phase transactions can now be prepared.
- session.close() didn't close all transactions when nested transactions were used.
- rollback() previously erroneously set the current transaction directly to the parent of the transaction that could be rolled back to.
- autoflush for commit() wasn't flushing for simple subtransactions.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
maintenance branch in branches/rel_0_3.
|
|
|
|
|
| |
- Deprecated BoundMetaData- use MetaData instead
- Removed DMD and BMD from documentation
|
| |
|
|
|
|
|
|
|
| |
- PropertyLoader figures out accurate remote_side collection based
on foreign_keys, legacy foreignkey, primary/secondaryjoin/polymorphic
- reworked lazyloader, sync to work straight off foreign_keys/
remote_side collections
|
|
|
|
|
|
| |
options to
Table objects [ticket:462]
|
|
|
|
| |
- applied Simon Wittber's ActiveMapper version_id_col patch for [ticket:348]
|
|
|
|
|
| |
a __autoload__ = True attribute in your inner mapping class. It does not
currently support autoloading relationships.
|
|
|
|
|
| |
fixes to unittests, mapper extension to work better with setting/unsetting extensions
objectstore objects get 'session' attribute
|
|
|
|
| |
both objectstores no longer subclass SessionContext, get at it via .context attribute instead
|
| |
|
|
|
|
| |
polymorphic behavior for initializing its real relation, added support + unittest for self-referential relationship
|
| |
|
|
|
|
|
|
| |
SessionContext
DynamicMetaData checks first for _engine before returning
|
|
|
|
|
| |
ActiveMapper. It looks like it is required by at least one person, so for
now the code will stay in!
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added implicit primary keys to ActiveMapper. Now, if you do not speicfy a
primary key on your objects when declaring them, an Integer primary key
called `id` will automatically be added to your objects for you.
* Commented out a large chunk of the process_relationships function that
should no longer be necessary thanks to some of the deferred mapper
compilation that was added in SQLAlchemy 0.2.3. I left it in the code, but
commented it out just in case this change causes a problem in someone's
else's code and I can put it back in if needed.
|
|
|
|
| |
Thanks to Charles Duffy for this patch!
|
| |
|
|
|
|
|
|
|
| |
class definitions better. The function was only looking at relationships, not
foreign keys, and was making some improper assumptions. The unit tests all
still pass, and now some of my own code actually works, regardless of the order
that I define the classes in.' 'lib/sqlalchemy/ext/activemapper.py
|
| |
|
|
|
|
| |
ordered set functionality supplied by a subclass of sets.Set
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the first place. The changes to process_relationships and to sqlachemy itself
were causing a double 'assign_mapper' call to cause issues. Now, we basically
defer calling assign_mapper until process_relationships in cases where there
are defined relationships.
Also, I moved ActiveMapper to always use the default engine, as there were a
lot of hacks inside ActiveMapper to allow for engine swapping. The use of the
default engine and the "global_connect" functionality significantly improves
the usability of ActiveMapper.
ActiveMapper will be getting a bit of a refactor/cleanup at some point in the
nearish future, as it has drifted a bit to complexity with the addition of some
features. For now, this should do the trick!
|
|
|
|
|
|
| |
changes is to ensure that relationships are properly detected and built in the
proper order. This should fix some problems that people were having with
ActiveMapper requiring classes to be declared in a specific order.
|
| |
|
|
|
|
| |
defined intermediate table.
|
|
|
|
| |
ForeignKey object on the fly. Also added ability to pass args and kwargs to Column constructor. ActiveMapper columns can have keyword args indexed and unique which will automatically create a index or a unique index. dburi in AutoConnectEngine can be a callable.
|
|
|