summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy
Commit message (Collapse)AuthorAgeFilesLines
...
| * | fix cymysql's _extact_error_code() for py3Hajime Nakagami2013-02-261-1/+4
| | |
| * | cython's _extract_error_code()Hajime Nakagami2013-02-251-1/+3
| | |
| * | merge from defaultHajime Nakagami2013-02-213-0/+27
| |\ \
| * | | add cymysql dialectHajime Nakagami2013-02-172-1/+30
| | | |
* | | | - add some more transaction states so that we deliver a more accurateMike Bayer2013-03-041-36/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | message for [ticket:2662]; after_commit() is called within "committed" state, not prepared, and no SQL can be emitted for prepared or committed - consolidate state assertions in session transaction, use just one method - add more unit tests for these assertions
* | | | yikes, print statement !Mike Bayer2013-03-031-3/+2
| | | |
* | | | fix non2.5 compat @property usageMike Bayer2013-03-031-4/+4
| | | |
* | | | dont need this conditional hereMike Bayer2013-03-031-4/+1
| | | |
* | | | - Improved checking for an existing backref name conflict duringMike Bayer2013-03-033-13/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mapper configuration; will now test for name conflicts on superclasses and subclasses, in addition to the current mapper, as these conflicts break things just as much. This is new for 0.8, but see below for a warning that will also be triggered in 0.7.11. - Improved the error message emitted when a "backref loop" is detected, that is when an attribute event triggers a bidirectional assignment between two other attributes with no end. This condition can occur not just when an object of the wrong type is assigned, but also when an attribute is mis-configured to backref into an existing backref pair. Also in 0.7.11. - A warning is emitted when a MapperProperty is assigned to a mapper that replaces an existing property, if the properties in question aren't plain column-based properties. Replacement of relationship properties is rarely (ever?) what is intended and usually refers to a mapper mis-configuration. Also in 0.7.11. [ticket:2674]
* | | | Can set/change the "cascade" attribute on a :func:`.relationship`Mike Bayer2013-03-023-40/+58
| | | | | | | | | | | | | | | | | | | | | | | | construct after it's been constructed already. This is not a pattern for normal use but we like to change the setting for demonstration purposes in tutorials.
* | | | - :meth:`.MetaData.create_all` and :meth:`.MetaData.drop_all` willMike Bayer2013-03-021-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | now accommodate an empty list as an instruction to not create/drop any items, rather than ignoring the collection. [ticket:2664]. This is a behavioral change and extra notes to the changelog and migration document have been added. - create a new test suite for exercising codepaths in engine/ddl.py
* | | | cleanupMike Bayer2013-03-021-8/+8
| |_|/ |/| |
* | | typoMike Bayer2013-02-261-1/+1
| | |
* | | - A clear error message is emitted if an event handlerMike Bayer2013-02-253-19/+131
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | attempts to emit SQL on a Session within the after_commit() handler, where there is not a viable transaction in progress. [ticket:2662] - rework how SessionTransaction maintains state, using symbols instead. - add lots of notes and cross-linking for session events. - add a link to :func:`.select()` within :meth:`.FromClause.select`.
* | | Detection of a primary key change within the processMike Bayer2013-02-251-1/+2
| | | | | | | | | | | | | | | | | | | | | of cascading a natural primary key update will succeed even if the key is composite and only some of the attributes have changed. [ticket:2665]
* | | this step is not neededMike Bayer2013-02-251-3/+0
| |/ |/|
* | - Added new helper function :func:`.was_deleted`, returns TrueMike Bayer2013-02-203-0/+27
|/ | | | | | | | | if the given object was the subject of a :meth:`.Session.delete` operation. - An object that's deleted from a session will be de-associated with that session fully after the transaction is committed, that is the :func:`.object_session` function will return None. [ticket:2658]
* see also for session commit, rollbackMike Bayer2013-02-111-1/+10
|
* The cx_oracle dialect will no longer run the bind parameter namesMike Bayer2013-02-081-1/+3
| | | | | | | through ``encode()``, as this is not valid on Python 3, and prevented statements from functioning correctly on Python 3. We now encode only if ``supports_unicode_binds`` is False, which is not the case for cx_oracle when at least version 5 of cx_oracle is used.
* Fixed bug whereby :meth:`.Query.yield_per` would set the executionMike Bayer2013-02-081-2/+2
| | | | | | options incorrectly, thereby breaking subsequent usage of the :meth:`.Query.execution_options` method. Courtesy Ryan Kelly. [ticket:2661]
* - fix exclusion hereMike Bayer2013-02-062-8/+5
| | | | - mysql doesn't reset table counter here so test differently
* port numeric tests to dialect suiteMike Bayer2013-02-062-1/+181
|
* - adding in requirementsMike Bayer2013-02-064-3/+110
| | | | - get test_naturalpks to be more generalized
* - add support for pulling in an external requirements fileMike Bayer2013-02-062-6/+68
| | | | - start filling in default versions of remaining requirements that are still only in test/
* - cleanup HasSequence and move it to test_sequencesMike Bayer2013-02-062-42/+58
|
* - add an explicit test for sequences "optional"Mike Bayer2013-02-062-1/+27
|
* - add an "empty_inserts" requirement target plus a suite testMike Bayer2013-02-065-0/+153
| | | | - add suite tests for basic explicit Sequence support, result-row column access (tests that name_normalize is set correctly among many other things)
* Fixed the consideration of the ``between()`` operatorMike Bayer2013-02-021-1/+1
| | | | | | so that it works correctly with the new relationship local/remote system. [ticket:1768]
* Fixed a bug regarding column annotations which in particularMike Bayer2013-02-021-1/+1
| | | | | | | | could impact some usages of the new :func:`.orm.remote` and :func:`.orm.local` annotation functions, where annotations could be lost when the column were used in a subsequent expression. [ticket:2660]
* more egregious long linesMike Bayer2013-02-022-38/+70
|
* formattingMike Bayer2013-02-022-4/+9
|
* Added a conditional import to the ``gaerdbms`` dialect which attemptsMike Bayer2013-02-021-6/+22
| | | | | | | to import rdbms_apiproxy vs. rdbms_googleapi to work on both dev and production platforms. Also now honors the ``instance`` attribute. Courtesy Sean Lynch. [ticket:2649]
* clean up ordering list docs, [ticket:2557]Mike Bayer2013-02-021-73/+92
|
* fix markupMike Bayer2013-02-021-0/+1
|
* The :meth:`.ColumnOperators.in_` operator will now coerceMike Bayer2013-02-021-0/+2
| | | | | values of ``None`` to :func:`.null`. [ticket:2496]
* Added a new argument to :class:`.Enum` and its baseMike Bayer2013-02-013-7/+65
| | | | | | | | | | | | :class:`.SchemaType` ``inherit_schema``. When set to ``True``, the type will set its ``schema`` attribute of that of the :class:`.Table` to which it is associated. This also occurs during a :meth:`.Table.tometadata` operation; the :class:`.SchemaType` is now copied in all cases when :meth:`.Table.tometadata` happens, and if ``inherit_schema=True``, the type will take on the new schema name passed to the method. The ``schema`` is important when used with the Postgresql backend, as the type results in a ``CREATE TYPE`` statement. [ticket:2657]
* version bumpMike Bayer2013-02-011-1/+1
|
* - add full docs for like()/ilike()Mike Bayer2013-01-281-0/+28
|
* add any/all to __all__Mike Bayer2013-01-281-1/+2
|
* - documentation for any()/all()Mike Bayer2013-01-281-12/+64
|
* Add ANY/ALL construct support for PostgreSQL's ARRAY typeAudrius Kažukauskas2013-01-282-1/+63
|
* - use SQL constructs here for databases that need to escape names like "data"Mike Bayer2013-01-271-5/+4
|
* Fixed bug where :meth:`.Table.tometadata` would fail if aMike Bayer2013-01-271-1/+1
| | | | | | :class:`.Column` had both a foreign key as well as an alternate ".key" name for the column. Also in 0.7.10. [ticket:2643]
* Fixing a code block in the PostgreSQL base dialect docstring.Taavi Burns2013-01-251-1/+1
|
* #2629Mike Bayer2013-01-251-0/+5
| | | | | insert().returning() raises an informative CompileError if attempted to compile on a dialect that doesn't support RETURNING.
* the consideration of a pending object asMike Bayer2013-01-243-8/+45
| | | | | | | | | | | 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]
* Fixed the (most likely never used) "@collection.link" collectionMike Bayer2013-01-211-10/+13
|\ | | | | | | | | | | | | | | | | 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]
| * Merged in lerks/sqlalchemy (pull request #36)Mike Bayer2013-01-211-9/+9
| |\ | | | | | | | | | Fix the collection.link decorator
| | * Fix the collection.link decoratorLuca Wehrstedt2013-01-161-9/+9
| | |
* | | - Made some fixes to the system of producing custom instrumentedMike Bayer2013-01-211-131/+88
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
View Lorry Controller Status