delta/python-packages/sqlalchemy.git/test/aaa_profiling/test_compiler.py, branch rel_1_2

Post black reformatting

2019-01-06T16:51:20+00:00

Applied on top of a pure run of black -l 79 in
I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9,  this set of changes
resolves all remaining flake8 conditions for those codes
we have enabled in setup.cfg.

Included are resolutions for all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I4f72d3ba1380dd601610ff80b8fb06a2aff8b0fe

Run black -l 79 against all source files

2019-01-06T06:31:01+00:00

This is a straight reformat run using black as is, with no edits
applied at all.

The black run will format code consistently, however in
some cases that are prevalent in SQLAlchemy code it produces
too-long lines.   The too-long lines will be resolved in the
following commit that will resolve all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9

- Added new checks for the common error case of passing mapped classes

2015-08-22T16:47:13+00:00

or mapped instances into contexts where they are interpreted as
SQL bound parameters; a new exception is raised for this.
fixes #3321

- rework profiling, zoomark tests into single tests so that

2014-08-16T23:49:07+00:00

they can be used under xdist

- fully flake8 test/aaa_profiling

2014-07-09T22:59:16+00:00

- rename multiple to backend, and apply backend to a large number of tests.

2014-03-24T15:33:53+00:00

- move out logging tests from test_execute to test_logging

- the raw 2to3 run

2013-04-27T23:53:57+00:00

- went through examples/ and cleaned out excess list() calls

A major fix to the way in which a select() object produces

2013-04-11T20:14:23+00:00

labeled columns when apply_labels() is used; this mode
produces a SELECT where each column is labeled as in
_, to remove column name collisions
for a multiple table select.   The fix is that if two labels
collide when combined with the table name, i.e.
"foo.bar_id" and "foo_bar.id", anonymous aliasing will be
applied to one of the dupes.  This allows the ORM to handle
both columns independently; previously, 0.7
would in some cases silently emit a second SELECT for the
column that was "duped", and in 0.8 an ambiguous column error
would be emitted.   The "keys" applied to the .c. collection
of the select() will also be deduped, so that the "column
being replaced" warning will no longer emit for any select()
that specifies use_labels, though the dupe key will be given
an anonymous label which isn't generally user-friendly.
[ticket:2702]

trying different approaches to test layout. in this one, the testing modules

2012-09-27T06:37:33+00:00

become an externally usable package but still remains within the main sqlalchemy parent package.
in this system, we use kind of an ugly hack to get the noseplugin imported outside of the
"sqlalchemy" package, while still making it available within sqlalchemy for usage by
third party libraries.

- [feature] To complement [ticket:2547], types

2012-08-17T22:35:25+00:00

can now provide "bind expressions" and
"column expressions" which allow compile-time
injection of SQL expressions into statements
on a per-column or per-bind level.   This is
to suit the use case of a type which needs
to augment bind- and result- behavior at the
SQL level, as opposed to in the Python level.
Allows for schemes like transparent encryption/
decryption, usage of Postgis functions, etc.
[ticket:1534]
- update postgis example fully.
- still need to repair the result map propagation
here to be transparent for cases like "labeled column".