| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
:class:`.Column` had both a foreign key as well as an
alternate ".key" name for the column. Also in 0.7.10.
[ticket:2643]
|
| | |
|
| |
|
|
|
| |
insert().returning() raises an informative CompileError if attempted
to compile on a dialect that doesn't support RETURNING.
|
| |
|
|
|
|
|
|
|
|
|
| |
an "orphan" has been modified to more closely match the
behavior as that of persistent objects, which is that the object
is expunged from the :class:`.Session` as soon as it is
de-associated from any of its orphan-enabled parents. Previously,
the pending object would be expunged only if de-associated
from all of its orphan-enabled parents. The new flag ``legacy_is_orphan``
is added to :func:`.orm.mapper` which re-establishes the
legacy behavior. [ticket:2655]
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
method, which fires off each time the collection is associated
or de-associated with a mapped object - the decorator
was not tested or functional. The decorator method
is now named :meth:`.collection.linker` though the name "link"
remains for backwards compatibility. Courtesy Luca Wehrstedt.
[ticket:2653]
|
| | |\
| | |
| | |
| | | |
Fix the collection.link decorator
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
collections, mainly that the usage of the @collection decorators
will now honor the __mro__ of the given class, applying the
logic of the sub-most classes' version of a particular collection
method. Previously, it wasn't predictable when subclassing
an existing instrumented class such as :class:`.MappedCollection`
whether or not custom methods would resolve correctly.
[ticket:2654]
- The undocumented (and hopefully unused) system of producing
custom collections using an ``__instrumentation__`` datastructure
associated with the collection has been removed, as this was a complex
and untested feature which was also essentially redundant versus the
decorator approach. Other internal simplifcations to the
orm.collections module have been made as well.
|
| | |
| |
| |
| | |
- documentation for mssql index options plus changelog and fixes
|
| |\ \
| | |
| | |
| | | |
Add extra mssql dialect options to Index
|
| | | | |
|
| | | | |
|
| | |/ |
|
| | |
| |
| |
| | |
output.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
functions, in addition to straight columns. Common modifiers
include using ``somecolumn.desc()`` for a descending index and
``func.lower(somecolumn)`` for a case-insensitive index, depending on the
capabilities of the target backend.
[ticket:695]
|
| |/ |
|
| |
|
|
|
| |
call in mssql information schema, fixes reflection
in Py3K. Also in 0.7.10. [ticket:2638]
|
| |
|
|
| |
is not maintainable
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
220/skip tests
- Fixed potential memory leak which could occur if an
arbitrary number of :class:`.sessionmaker` objects
were created. The anonymous subclass created by
the sessionmaker, when dereferenced, would not be garbage
collected due to remaining class-level references from the
event package. This issue also applies to any custom system
that made use of ad-hoc subclasses in conjunction with
an event dispatcher. Also in 0.7.10. [ticket:2650]
|
| |
|
|
|
|
|
|
|
|
|
| |
- Fixed a regression whereby the "collation" parameter
of the character types CHAR, NCHAR, etc. stopped working,
as "collation" is now supported by the base string types.
The TEXT, NCHAR, CHAR, VARCHAR types within the
MSSQL dialect are now synonyms for the base types.
- move out the type rendering tests into DB-agnostic tests
and remove some of the old "create" statements. tests here
are still very disorganized.
|
| |\
| |
| |
| | |
support identity columns that are not part of the primary key)
|
| | | |
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
primary key
|
| | | |
| | |
| | |
| | |
| | | |
where an entity may be ``None`` without throwing an error.
[ticket:2640]
|
| | | |
| | |
| | |
| | |
| | |
| | | |
INSERT/UPDATE bound parameters that need to be passed, so that
it's more easily identifiable when writing custom bind-handling
code. [ticket:2648]
|
| | | |
| | |
| | |
| | | |
- apply a consistent approach to the "see if method X is implemented" conditionals
|
| | | |
| | |
| | |
| | |
| | | |
inside of an :func:`.expression.insert` construct would produce an
error regarding a parameter issue in the ``self_group()`` method.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
associated with the ORM or its extensions can be retrieved.
This fulfills the common request of being able to inspect
all :class:`.QueryableAttribute` descriptors in addition to
extension types such as :class:`.hybrid_property` and
:class:`.AssociationProxy`. See :attr:`.Mapper.all_orm_descriptors`.
|
| | | |
| | |
| | |
| | | |
object has no attribute 'group'
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
on regular append/remove history
- fix the real cause of the original #2637 issue, backrefs call upon
the "pop()" method now which wasn't implemented for Dynamic
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
that's
the wrong behavior, and for the original #2637 issue we will have to fix the
association proxy, which is #2642
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
DynamicAttributeImpl
- Fixes to the "dynamic" loader on :func:`.relationship`, includes
that backrefs will work properly even when autoflush is disabled,
history events are more accurate in scenarios where multiple add/remove
of the same object occurs, as can often be the case in conjunction
with the association proxy. [ticket:2637]
|
| | | |
| | |
| | |
| | | |
- add "extend()" to AppenderQuery
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
0.7.9, to intercept legacy SQLite quoting characters when reflecting
foreign keys. In addition to intercepting double quotes, other
quoting characters such as brackets, backticks, and single quotes
are now also intercepted. [ticket:2568]
|
| | | |
| | |
| | |
| | |
| | | |
:func:`.aliased` construct without it interfering with the entities
being selected. [ticket:2635]
|