| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| | |
Change _process_colparams method to remove duplicate isinstance calls
and try to speed up processing of the parameters.
|
| |
| |
| |
| |
| | |
Remove added dict comprehensions that make this patch set non python 2.6
compatible.
|
| |
| |
| |
| |
| |
| | |
Instead of checking multiple times if parameters are a dictionary in the
form of a tuple or list of value pairs, we check it only once and then
store it in the statement so it can be used on compilation time.
|
| |
| |
| |
| |
| |
| |
| | |
Postpone as much as possible the change of update parameters to
OrderedDict from list or tuple of pairs.
This way we won't have problems with query's update method.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To avoid penalties for updates that do not require ordering, we will
only use OrderedDict for updates that receive a tuple or list of pairs,
and all kinds of dictionaries (dict, sqlalchemy's OrderedDict, or
collections.OrderedDict) will be treateated as unordered updates, just
like we were doing before.
This way this new feature will not change how updates behave for any
existing code and will only affect those that use the new ordered
feature.
This patch reverts update tests to how they were before as well as adds
a couple of tests to confirm that OrderedDicts are really treated like
normal dicts.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In some DBs the UPDATE operation is order dependent, so the operation
behaves differently depending on the order of the values.
As an example, imagine a volumes table with columns 'status' and
'previous_status' and we want to update a volume that has 'available' in
the status column.
If the SQL query is performed as:
UPDATE volumes SET previous_status=status, status='new' WHERE id=1;
This will result in a volume with 'new' status and 'available'
previous_status both on SQLite and MariaDB, but if we reverse the
columns:
UPDATE volumes SET status='new', previous_status=status WHERE id=1;
We will get the same result in SQLite but will result in a volume with
status and previous_status set to 'new' in MariaDB, which is not what we
want.
So order must be taken into consideration in some cases and it should be
allowed to ve specified via the Query update method or the values method
of an update.
This patch fixes this issue by preserving the order of parameters in
updates and allowing to receive not only dictionaries in update and
values but also ordered dictionaries and list/tuples of value pairs
(like dict and OrderedDict do).
fixes #3541
|
|\ \ |
|
| | |
| | |
| | | |
Thanks to Mike Bayer for suggesting a simpler refactoring.
|
| | | |
|
|\ \ \ |
|
| |/ / |
|
| | |
| | |
| | |
| | | |
"auto" now so True can indicate the dialect would support this
|
|\ \ \ |
|
| | | |
| | | |
| | | | |
Docstring typo keysowrds => keywords
|
|/ / /
| | |
| | |
| | | |
"auto", doesn't matter if there's a default here
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
"auto increment" column has been changed, such that autoincrement
is no longer implicitly enabled for a :class:`.Table` that has a
composite primary key. In order to accommodate being able to enable
autoincrement for a composite PK member column while at the same time
maintaining SQLAlchemy's long standing behavior of enabling
implicit autoincrement for a single integer primary key, a third
state has been added to the :paramref:`.Column.autoincrement` parameter
``"auto"``, which is now the default. fixes #3216
- The MySQL dialect no longer generates an extra "KEY" directive when
generating CREATE TABLE DDL for a table using InnoDB with a
composite primary key with AUTO_INCREMENT on a column that isn't the
first column; to overcome InnoDB's limitation here, the PRIMARY KEY
constraint is now generated with the AUTO_INCREMENT column placed
first in the list of columns.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
symbols with names quoted to force all-lower-case would not be
identified properly in reflection queries. The :class:`.quoted_name`
construct is now applied to incoming symbol names that detect as
forced into all-lower-case within the "name normalize" process.
fixes #3548
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
may be construed as the Python "and" keyword
- add notes to ORM tutorial for beginners that Python "and" keyword
is not to be used
fixes #3545
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
implicit schema
- repair the CREATE INDEX ddl for schemas
- update provisioning to include support for setting up ATTACH DATABASE up front
for the test_schema; enable "schemas" testing for SQLite
- changelog / migration notes for new SQLite schema support
- include the "schema" as the "remote_schema" when we reflect SQLite FKs
|
|\ \ \ |
|
| | | |
| | | |
| | | | |
Should return "main" and the names of attached databases.
|
| | | | |
|
| | | | |
|
| |/ /
|/| |
| | |
| | |
| | | |
finally, test_resultset and test_insert_exec. Update all
idioms within these.
|
| | |
| | |
| | | |
Also add a couple of missing tests.
|
| | |
| | |
| | |
| | | |
- changelog / version note finishing
|
| |/
|/| |
|
| |
| |
| |
| | |
(cherry picked from commit 5db5e18d3babdb3ee857c075c774a585505b78ce)
|
| |
| |
| |
| | |
(cherry picked from commit 81eefe038ea44a5314002483dde9cf00580df1bd)
|
| |
| |
| |
| | |
(cherry picked from commit ea084bdc656a6a64db1ee582630d415bc8154505)
|
| |
| |
| |
| |
| | |
kinds of internal column loader options within internal logging.
fixes #3539
|
| |
| |
| |
| |
| |
| |
| | |
as part of :ticket:`3424` to allow disabling of the MSSQL dialect's
attempts to create aliases for schema-qualified tables, now defaults
to False; the old behavior is now disabled unless explicitly turned on.
fixes #3434
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
which indicates to the ORM that a positive set of None should be
persisted as the value NULL, instead of omitting the column from
the INSERT statement. This feature is used both as part of the
implementation for :ticket:`3514` as well as a standalone feature
available on any type. fixes #3250
- add new documentation section illustrating the "how to force null"
use case of #3250
- alter our change from #3514 so that the class-level flag is now
called "should_evaluate_none"; so that "evaluates_none" is now
a generative method.
|
| |
| |
| |
| |
| |
| |
| | |
to a :class:`.types.Enum` or :class:`.postgresql.ENUM` subtype
will now emit the expected "CREATE TYPE" and "DROP TYPE" DDL when
the type is used within a "CREATE TABLE" or "DROP TABLE".
fixes #2729
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
expression element which is late-evaluated at compile time. Previously,
the function was only a conversion function which would handle different
expression inputs by returning either a :class:`.Label` of a column-oriented
expression or a copy of a given :class:`.BindParameter` object,
which in particular prevented the operation from being logically
maintained when an ORM-level expression transformation would convert
a column to a bound parameter (e.g. for lazy loading).
fixes #3531
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
to use mapper.cascade_iterator() for this purpose as it was not really
designed for that use case. Add docs to cascade_iterator() pointing
to the recipe. fixes #3498
|
| |
| |
| |
| |
| |
| | |
Fixes #3528
Signed-off-by: Jason Myers <jason@jasonamyers.com>
|
| | |
|
|\ \
| | |
| | |
| | | |
fix typo in session events docs
|
| | | |
|
|\ \ \
| | | |
| | | | |
Minor grammar fix for capitalisation in session docs
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
:meth:`.Session.bulk_save_objects` and related bulk methods have
been scaled back to the extent that this functionality is not
currently used, e.g. checks for column default values to be
fetched after an INSERT or UPDATE statement.
fixes #3526
|