delta/python-packages/sqlalchemy.git/test/dialect/test_oracle.py, branch pr/304 github.com: zzzeek/sqlalchemy.git Adapt "FOR UPDATE OF" with Oracle limit/offset 2016-07-05T22:30:25+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-07-05T16:48:41+00:00 f2ee514c757fc9ec33afaddc2a7b96d08b83a164 This modifies the Oracle ROWNUM limit/offset approach to accommodate for the "OF" clause in a "FOR UPDATE" phrase. The column expressions must be added to the selected subquery if necessary and adapted on the outside. Change-Id: Ia71b5fc4df6d326e73863f8ae9f96e8f1a5acfc1 Fixes: #3741 
This modifies the Oracle ROWNUM limit/offset approach
to accommodate for the "OF" clause in a "FOR UPDATE"
phrase.  The column expressions must be added to the selected
subquery if necessary and adapted on the outside.

Change-Id: Ia71b5fc4df6d326e73863f8ae9f96e8f1a5acfc1
Fixes: #3741
Add 'FOR NO KEY UPDATE' / 'FOR KEY SHARE' support for Postgresql 2016-06-08T15:24:57+00:00 Sergey Skopin sa.skopin@gmail.com 2016-05-31T14:02:08+00:00 3ebd1b30eb392ff62f08f0755e79a228d61ba7d2 Adds ``key_share=True`` for with_for_update(). Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Change-Id: I74e0c3fcbc023e1dc98a1fa0c7db67b4c3693a31 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/279 
Adds ``key_share=True`` for with_for_update().

Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Change-Id: I74e0c3fcbc023e1dc98a1fa0c7db67b4c3693a31
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/279
Add SKIP LOCKED support for Postgresql, Oracle 2016-06-02T21:46:16+00:00 Jack Zhou univerio@gmail.com 2016-05-31T14:01:46+00:00 e8f97c9e357ed0793ce11086823f83aa4a8bb4ad 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 
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
- add missing __backend__ directives so that oracle tests actually run with --backend-only 2016-02-08T19:16:40+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-02-08T19:16:40+00:00 860d07ff89a8fd8b6a4d3036837c0e129d6cc233 






- detect "Enterprise" and assume compression stuff isn't available
2016-02-08T19:08:03+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-02-08T19:08:03+00:00

308244a90b95d2b78ed8f76e3af0d0c3d2329720

if not





if not







- adjust the MultiSchemaTest to handle multiple test_schemas / processes at the
2016-02-08T18:35:36+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-02-08T18:35:36+00:00

80853059a9f4bebfe41f9c340eddc2d6a86ef70f

same time





same time







- adjust to allow dblink tests to work with multiprocess users.
2016-02-08T18:13:39+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-02-08T18:13:39+00:00

7e619d0be41afc3b6cd5e5fceba9dbc5f39b012d

unfortunately the synonym doesn't work for SQL statements here
when the dblink is on a different user, testing this is not really
critical so just removed it.





unfortunately the synonym doesn't work for SQL statements here
when the dblink is on a different user, testing this is not really
critical so just removed it.







- Fixed bug in Oracle dialect where reflection of tables and other
2015-10-05T13:49:34+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2015-10-05T13:49:34+00:00

4578ab54a5b849fdb94a7032987f105b7ec117a4

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





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







- fix some more result_map calls
2015-03-08T18:16:59+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2015-03-08T18:16:59+00:00

7c9a0e18beadd73c94b8de4cba06eae2d78d2061












- the change for #918 was of course not nearly that simple.
2015-03-08T04:03:27+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2015-03-08T03:51:12+00:00

17b2fd3fba8eef5bdd4040f2d71c75e4aeb4e215

The "wrapping" employed by the mssql and oracle dialects using the
"iswrapper" argument was not being used intelligently by the compiler,
and the result map was being written incorrectly, using
*more* columns in the result map than were actually returned by
the statement, due to "row number" columns that are inside the
subquery.   The compiler now writes out result map on the
"top level" select in all cases
fully, and for the mssql/oracle wrapping case extracts out
the "proxied" columns in a second step, which only includes
those columns that are proxied outwards to the top level.

This change might have implications for 3rd party dialects that
might be imitating oracle's approach.   They can safely continue
to use the "iswrapper" kw which is now ignored, but they may
need to also add the _select_wraps argument as well.





The "wrapping" employed by the mssql and oracle dialects using the
"iswrapper" argument was not being used intelligently by the compiler,
and the result map was being written incorrectly, using
*more* columns in the result map than were actually returned by
the statement, due to "row number" columns that are inside the
subquery.   The compiler now writes out result map on the
"top level" select in all cases
fully, and for the mssql/oracle wrapping case extracts out
the "proxied" columns in a second step, which only includes
those columns that are proxied outwards to the top level.

This change might have implications for 3rd party dialects that
might be imitating oracle's approach.   They can safely continue
to use the "iswrapper" kw which is now ignored, but they may
need to also add the _select_wraps argument as well.