delta/python-packages/sqlalchemy.git/test/orm, branch pr/299

Spelling fixes

2016-08-08T13:39:15+00:00

Clarify order_by(False)

2016-07-29T22:57:04+00:00

It wasn't clear how this differs from order_by(None);
add more tests and document that this has to do with whether or
not mapper.order_by will be re-enabled as well.

Change-Id: I332e8ac60c999b38c5a243f1cb72de3cf77891b6

Allow None to cancel Query.group_by()

2016-07-29T22:44:34+00:00

This replicates the same behavior as order_by().

order_by() will also be updated to deprecate passing
of False as this is no longer functionally different
than passing None.

Change-Id: I2fc05d0317d28b6c83373769a48f7eea32d56290
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/297

- a variety of test adjustments to accomodate for MySQL 5.7

2016-07-24T20:36:27+00:00

Change-Id: Ied4245433d0d7b469dae6e7394c4931d8405f387

Remove same-named relationship warning

2016-07-19T16:36:21+00:00

Removed a warning that dates back to 0.4 which emits when a same-named
relationship is placed on two mappers that inherits via joined or
single table inheritance.   The warning does not apply to the
current unit of work implementation.

Change-Id: If528ec3a2f4dc60712d9044fd1ec6c4dfbf0eadb
Fixes: #3749

Deprecate FromClause.count()

2016-06-14T15:48:04+00:00

count() here is misleading in that it not only
counts from an arbitrary column in the table, it also
does not make accommodations for DISTINCT, JOIN, etc.
as the ORM-level function does.  Core should not be
attempting to provide a function like this.

Change-Id: I9916fc51ef744389a92c54660ab08e9695b8afc2
Fixes: #3724

Use the "committed" values when extracting many-to-one lazyload value

2016-06-08T16:57:21+00:00

The scalar object set() method calls upon the lazy loader
to get at the "old" value of the attriute, however doesn't
ensure that the "committed" value of the foreign key attributes
is used.  If the user has manipulated these attributes and they
themselves have pending, non committed changes, we get the
"new" value which these attributes would have set up if they
were flushed.  "old" vs "new" value is always about how the
value has changed since the load, so we always have to use the
DB-persisted values for everything when looking for "old".

Change-Id: I82bdc40ad0cf033c3a98f3361776cf3161542cd6
Fixes: #3708

Add 'FOR NO KEY UPDATE' / 'FOR KEY SHARE' support for Postgresql

2016-06-08T15:24:57+00:00

Adds ``key_share=True`` for with_for_update().

Co-authored-by: Mike Bayer 
Change-Id: I74e0c3fcbc023e1dc98a1fa0c7db67b4c3693a31
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/279

Add "render_nulls" flag to bulk_insert as optional performance optimization

2016-06-06T20:22:11+00:00

Currently, ``Session.bulk_insert_mappings`` omits NULL values which
causes it to break up batches of inserts based on which batches
contain NULL and which do not.

By adding this flag, the same columns are rendered in the INSERT
for all rows allowing them to be batched.  The downside is that
server-side defaults are omitted.

Doctext-author: Mike Bayer 
Change-Id: Iec5969304d4bdbf57290b200331bde02254aa3a5
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/243

Add SKIP LOCKED support for Postgresql, Oracle

2016-06-02T21:46:16+00:00

This adds `SELECT ... FOR UPDATE SKIP LOCKED`/
`SELECT ... FOR SHARE SKIP LOCKED` rendering.

Change-Id: Id1dc4f1cafc1de23f397a6f73d54ab2c58d5910d
Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/86