summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'origin/pr/200' into pr200pr200Mike Bayer2015-10-098-41/+196
|\
| * Reduce the numbers of calls to isinstancepr/200Gorka Eguileor2015-10-083-35/+33
| | | | | | | | | | Change _process_colparams method to remove duplicate isinstance calls and try to speed up processing of the parameters.
| * Remove dict comprehension for py26 compatibilityGorka Eguileor2015-10-052-5/+5
| | | | | | | | | | Remove added dict comprehensions that make this patch set non python 2.6 compatible.
| * Only check once if parameters are orderedGorka Eguileor2015-10-024-35/+36
| | | | | | | | | | | | 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 parameters change in ordered updatesGorka Eguileor2015-09-305-28/+26
| | | | | | | | | | | | | | 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.
| * Only preserve order in updates if tuple/dictGorka Eguileor2015-09-2911-50/+134
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * Preserve order in update methodGorka Eguileor2015-09-2410-32/+106
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge remote-tracking branch 'origin/pr/203'Mike Bayer2015-10-094-19/+22
|\ \
| * | Remplement Query.one() in terms of .one_or_none()pr/203Eric Siegerman2015-09-284-19/+22
| | | | | | | | | Thanks to Mike Bayer for suggesting a simpler refactoring.
* | | - this was supposed to be client-side SQL default not server sideMike Bayer2015-10-091-1/+1
| | |
* | | Merge remote-tracking branch 'origin/pr/205'Mike Bayer2015-10-091-0/+12
|\ \ \
| * | | Doc fixpr/205Eric Siegerman2015-09-281-0/+12
| |/ /
* | | - open up autoincrement for columns that have a default; autoinc is usuallyMike Bayer2015-10-084-49/+52
| | | | | | | | | | | | "auto" now so True can indicate the dialect would support this
* | | Merge remote-tracking branch 'origin/pr/208'Mike Bayer2015-10-081-1/+1
|\ \ \
| * | | Update base.pypr/208Peter Demin2015-10-071-1/+1
| | | | | | | | | | | | Docstring typo keysowrds => keywords
* | | | - for DB's w/o a real "autoincrement", reflection should be returningMike Bayer2015-10-073-3/+3
|/ / / | | | | | | | | | "auto", doesn't matter if there's a default here
* | | - The system by which a :class:`.Column` considers itself to be anMike Bayer2015-10-0722-160/+755
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "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.
* | | - Fixed bug in Oracle dialect where reflection of tables and otherMike Bayer2015-10-053-0/+40
| | | | | | | | | | | | | | | | | | | | | | | | 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
* | | - add an additional note regarding select_from, fixes #3546Mike Bayer2015-10-021-0/+10
| | |
* | | - remove ambiguous use of the phrase "joined together by AND" as thisMike Bayer2015-10-012-5/+12
| | | | | | | | | | | | | | | | | | | | | 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
* | | - bzzt, fix the base _post_configure_engine() call to not failMike Bayer2015-09-291-1/+1
| | |
* | | - limit the search for schemas to not include "temp", which is sort of an ↵Mike Bayer2015-09-286-34/+93
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge remote-tracking branch 'origin/pr/198' into pr198Mike Bayer2015-09-282-0/+12
|\ \ \
| * | | Support get_schema_names for SQLitepr/198Brian Van Klaveren2015-09-091-0/+5
| | | | | | | | | | | | Should return "main" and the names of attached databases.
| * | | Support get_schema_names for SQLiteBrian Van Klaveren2015-09-091-0/+7
| | | |
* | | | - fix bool testMike Bayer2015-09-271-1/+1
| | | |
* | | | - break out critical aspects of test_query into their own testsMike Bayer2015-09-273-1416/+1585
| |/ / |/| | | | | | | | | | | finally, test_resultset and test_insert_exec. Update all idioms within these.
* | | Fix sqlalchemy.ext.baked.Result.one_or_none() exception messagepr/202Eric Siegerman2015-09-242-4/+27
| | | | | | | | | Also add a couple of missing tests.
* | | - replicate Query.one_or_none to BakedQueryMike Bayer2015-09-244-6/+59
| | | | | | | | | | | | - changelog / version note finishing
* | | Add Query.one_or_none()pr/201Eric Siegerman2015-09-244-1/+96
| |/ |/|
* | Add a lot more detailEric Siegerman2015-09-231-3/+22
| | | | | | | | (cherry picked from commit 5db5e18d3babdb3ee857c075c774a585505b78ce)
* | Add some markupEric Siegerman2015-09-231-2/+2
| | | | | | | | (cherry picked from commit 81eefe038ea44a5314002483dde9cf00580df1bd)
* | A few minor rewordingsEric Siegerman2015-09-231-3/+3
| | | | | | | | (cherry picked from commit ea084bdc656a6a64db1ee582630d415bc8154505)
* | - Fixed rare TypeError which could occur when stringifying certainMike Bayer2015-09-233-2/+20
| | | | | | | | | | kinds of internal column loader options within internal logging. fixes #3539
* | - The ``legacy_schema_aliasing`` flag, introduced in version 1.0.5Mike Bayer2015-09-196-79/+96
| | | | | | | | | | | | | | 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
* | - Added a new type-level modifier :meth:`.TypeEngine.evaluates_none`Mike Bayer2015-09-197-11/+259
| | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | - The use of a :class:`.postgresql.ARRAY` object that refersMike Bayer2015-09-194-1/+91
| | | | | | | | | | | | | | 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
* | - fixes for the ORM side test for #3531.Mike Bayer2015-09-171-3/+6
| |
* | - The :func:`.type_coerce` construct is now a fully fledged CoreMike Bayer2015-09-1610-65/+373
| | | | | | | | | | | | | | | | | | | | | | 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
* | - fix incorrect example in inheritance docsMike Bayer2015-09-151-3/+3
| |
* | - add new entry for sharing of Engine across process boundariesMike Bayer2015-09-141-0/+81
| |
* | - call it deque, since you can really pop from either sideMike Bayer2015-09-101-5/+5
| |
* | - add a new FAQ recipe for "walk all objects", replacing the needMike Bayer2015-09-102-4/+84
| | | | | | | | | | | | 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
* | Correcting the Hybrid Property ExampleJason Myers2015-09-101-1/+1
| | | | | | | | | | | | Fixes #3528 Signed-off-by: Jason Myers <jason@jasonamyers.com>
* | - profile updateMike Bayer2015-09-081-1/+1
| |
* | Merged in bsmithgall/sqlalchemy/event-doc-link-fix (pull request #60)Mike Bayer2015-09-081-1/+1
|\ \ | | | | | | | | | fix typo in session events docs
| * | fix typo in session events docsbsmithgall2015-09-071-1/+1
| | |
* | | Merge pull request #197 from davidjb/mastermike bayer2015-09-081-1/+1
|\ \ \ | | | | | | | | Minor grammar fix for capitalisation in session docs
| * | | Minor grammar fix for capitalisation in session docspr/197David\ Beitey2015-08-281-1/+1
| | | |
* | | | - Internal calls to "bookkeeping" functions withinMike Bayer2015-09-083-50/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | :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