| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Improve screen output to illustrate which server version is
running for a particular database config, and additionally
allow full overriding for the backend-specific targets in
tox.ini via environment variables, so that CI can inject
multiple server urls for a particular database such as MySQL/MariaDB.
Change-Id: Ibf443bb9fb82e4563efd1bb66058fa9989aa2fda
|
|
|
|
|
|
| |
in mariadb 10.2. more mariadb fixes coming
Change-Id: I6e3a94ae7340772663677b1082506adbb2d84a38
|
|
|
|
|
|
| |
Until https://github.com/pytest-dev/pytest-xdist/issues/196 is fixed
Change-Id: I7dfd268e6078373ccaa0b5c13f9b6ffa1b2fd4b2
|
|
|
|
|
| |
Change-Id: I65ebe00fa7372151210a1f177f5417ac08c41586
(cherry picked from commit 90ef2c2314187b00e037a4b347b5d62eec387aac)
|
|
|
|
|
|
| |
- restore unreleased directories
Change-Id: Ia5c1142ffbdba6372f800c2e2521660ab62d9c4f
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixed performance regression caused by the fix for :ticket:`3937` where
cx_Oracle as of version 5.3 dropped the ``.UNICODE`` symbol from its
namespace, which was interpreted as cx_Oracle's "WITH_UNICODE" mode being
turned on unconditionally, which invokes functions on the SQLAlchemy
side which convert all strings to unicode unconditionally and causing
a performance impact. In fact, per cx_Oracle's author the
"WITH_UNICODE" mode has been removed entirely as of 5.1, so the expensive unicode
conversion functions are no longer necessary and are disabled if
cx_Oracle 5.1 or greater is detected under Python 2. The warning against
"WITH_UNICODE" mode that was removed under :ticket:`3937` is also restored.
Change-Id: Iddd38d81a5adb27c953a5ee2eae5529a21da16e1
Fixes: #4035
|
|/
|
|
|
|
|
| |
- 1.0.19
Change-Id: I476213fe905a51826feeddb4e1c97416c2bac558
(cherry picked from commit f7beeb389d242d1c0fe56c22349f5dcc23722bde)
|
|
|
|
| |
Change-Id: I9aa6e891ca896b90b97fbd0e52f0ad73494e38d7
|
| |
|
|
|
|
|
|
| |
(cherry picked from commit ad5626cdb9b4d4ac38b2169dc7377d4bc66ee549)
Change-Id: Icd2f3ce68451e609c0d1c116256c2e1cf8baf7eb
|
|
|
|
|
|
| |
(cherry picked from commit f00391a070d9031941bb1c17aecb265b566a6a5b)
Change-Id: I243a63d084d4b369ded7969d78e3ab033f6189bd
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Fixed issue in testing fixtures which was incompatible with a change
made as of Python 3.6.2 involving context managers.
Change-Id: I0f12aa6cc15cba89153f7e4888ac347e7ce599c7
Fixes: #4034
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added ``KeyError`` checks to all methods within
:class:`.WeakInstanceDict` where a check for ``key in dict`` is
followed by indexed access to that key, to guard against a race against
garbage collection that under load can remove the key from the dict
after the code assumes its present, leading to very infrequent
``KeyError`` raises.
Change-Id: I881cc2899f7961d29a0549f44149a2615ae7a4ea
Fixes: #4030
|
|\ \
| |/
|/| |
|
| |
| |
| | |
Improve the wording of how sessions commit changes.
|
|/
|
|
|
| |
Change-Id: I588eebd027b4ad3428bd522f36a6f1cd77f105bb
(cherry picked from commit 39c72682b85c1d3912ced383733d03eca7a43845)
|
|
|
|
|
|
|
|
|
|
|
| |
so that we no longer have to rely upon merges within
the changelog files. because gerrit doesn't allow us
to use custom merge engines unlike git, we have no ability
to merge multiple changes into the changelog files without
going through conflicts. new version of changelog
in git supports these new patterns.
Change-Id: I588eebd027b4ad3428bd522f36a6f1cd77f105bb
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixed bug involving JSON NULL evaluation logic added in 1.1 as part
of :ticket:`3514` where the logic would not accommodate ORM
mapped attributes named differently from the :class:`.Column`
that was mapped.
Change-Id: I1848afcfb63ad7f074f315d8d3097666069b42be
Fixes: #4031
|
|/
|
|
|
|
|
|
|
|
| |
Fixed issue where adding additional non-entity columns to
a query that includes an entity with subqueryload relationships
would fail, due to an inspection added in 1.1.11 as a result of
:ticket:`4011`.
Change-Id: I8ef082be649125bdc07b428cb9b0a77a65d73671
Fixes: #4033
|
|\ |
|
| |
| |
| | |
The Session class was used instead of the session instance which resulted in an attribute error.
|
|\ \ |
|
| |/ |
|
|/
|
|
| |
Change-Id: I95ff7f4bb0048b363987344d359f252469b23b79
|
| |
|
| |
|
|
|
|
| |
Change-Id: I660a4966e7375859058025ef132c595f74293e4c
|
|
|
|
| |
Change-Id: Ie1bdcf2773f3de96d5ca26ebf80657e5d72c70f9
|
|
|
|
|
|
| |
inventory on every build not worth it
Change-Id: I3c4506b246d0f327c4b56afa723975daee984476
|
|
|
|
| |
Change-Id: Ice3eeb8312fcb5a4d586113ee3e52be90fbcd95e
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added new keywords :paramref:`.Sequence.cache` and
:paramref:`.Sequence.order` to :class:`.Sequence`, to allow rendering
of the CACHE parameter understood by Oracle and PostgreSQL, and the
ORDER parameter understood by Oracle. Pull request
courtesy David Moore.
Change-Id: I082c3f8ef56ef89dbaad5da9d5695be5313b0614
Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/96
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added ``.autocommit`` attribute to :class:`.scoped_session`, proxying
the ``.autocommit`` attribute of the underling :class:`.Session`
currently assigned to the thread. Pull request courtesy
Ben Fagin.
Change-Id: Iff741978bd67762f4c7375a23cc151b26192042b
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/372
|
|/
|
|
| |
Change-Id: I23ccfebfbaaf40739a4a538d232875135a5cd04c
|
|
|
|
|
|
|
|
|
|
|
| |
Added support for MySQL's ON DUPLICATE KEY UPDATE
MySQL-specific :class:`.mysql.dml.Insert` object.
Pull request courtesy Michael Doronin.
Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Resolves: #4009
Change-Id: Ic71424f3c88af6082b48a910a2efb7fbfc0a7eb4
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/365
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The result processor for the :class:`.Float` type now unconditionally
runs values through the ``float()`` processor if the dialect
specifies that it also supports "native decimal" mode. While most
backends will deliver Python ``float`` objects for a floating point
datatype, the MySQL backends in some cases lack the typing information
in order to provide this and return ``Decimal`` unless the float
conversion is done.
Change-Id: I638f1480fb00a507036efaf0e0080f26893d98ad
Fixes: #4020
|
|\
| |
| |
| | |
deferred_expression"
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The attributeimpl for a deferred_expression does not
support a scalar loader, add new configurability so that
the impl can have this flag turned off. Document
that the with_expression() system currently does not
offer any deferred loading.
To eliminate confusion over "deferred", which refers to
lazy loading of column attributes, and "with_expression",
which refers to an attribute that is explicitly at
query time only, rename deferred_expression to query_expression.
Change-Id: I07c4a050ed68c79ccbde9492e9de1630b7470d74
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
The rules for type coercion between :class:`.Numeric`, :class:`.Integer`,
and date-related types now include additional logic that will attempt
to preserve the settings of the incoming type on the "resolved" type.
Currently the target for this is the ``asdecimal`` flag, so that
a math operation between :class:`.Numeric` or :class:`.Float` and
:class:`.Integer` will preserve the "asdecimal" flag as well as
if the type should be the :class:`.Float` subclass.
Change-Id: Idfaba17220d6db21ca1ca4dcb4c19834cd397817
Fixes: #4018
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added some extra strictness to the handling of Python "float" values
passed to SQL statements. A "float" value will be associated with the
:class:`.Float` datatype and not the Decimal-coercing :class:`.Numeric`
datatype as was the case before, eliminating a confusing warning
emitted on SQLite as well as unecessary coercion to Decimal.
Change-Id: I1bb1810ff1d198c0d929ccba5656e55401d74119
Fixes: #4017
|
| | |
|
|/
|
|
|
| |
Change-Id: Ie0b78c79367933486528ca0ba686d4a9f16922b1
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/370
|
|
|
|
|
|
|
|
|
|
| |
Added a new feature :func:`.orm.with_expression` that allows an ad-hoc
SQL expression to be added to a specific entity in a query at result
time. This is an alternative to the SQL expression being delivered as
a separate element in the result tuple.
Change-Id: Id8c479f7489fb02e09427837c59d1eabb2a6c014
Fixes: #3058
|