<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/python-packages/sqlalchemy.git/test/sql, branch pr/259</title>
<subtitle>github.com: zzzeek/sqlalchemy.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/'/>
<entry>
<title>- move all resultproxy tests intio test_resultset, adapted from</title>
<updated>2016-03-30T21:44:04+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2016-03-30T21:44:04+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=bdd29fd56b0d03c4c0124e3a5643709b0ce7016a'/>
<id>bdd29fd56b0d03c4c0124e3a5643709b0ce7016a</id>
<content type='text'>
03d35a833cff68013781640b1192d079ab7e1154 in master (not cherry-picked)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
03d35a833cff68013781640b1192d079ab7e1154 in master (not cherry-picked)
</pre>
</div>
</content>
</entry>
<entry>
<title>- Fixed bug where the negation of an EXISTS expression would not</title>
<updated>2016-03-21T14:58:08+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2016-03-21T14:57:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=dfe49c7b7f0c83ced11fdbceef14d89c82647f0b'/>
<id>dfe49c7b7f0c83ced11fdbceef14d89c82647f0b</id>
<content type='text'>
be properly typed as boolean in the result, and also would fail to be
anonymously aliased in a SELECT list as is the case with a
non-negated EXISTS construct.
fixes #3682

(cherry picked from commit 07a4b6cbcda6e6ee6e67893c5a5d2fd01e5f125f)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
be properly typed as boolean in the result, and also would fail to be
anonymously aliased in a SELECT list as is the case with a
non-negated EXISTS construct.
fixes #3682

(cherry picked from commit 07a4b6cbcda6e6ee6e67893c5a5d2fd01e5f125f)
</pre>
</div>
</content>
</entry>
<entry>
<title>- move out unconsumed names tests from test_compiler out to test_insert, test_update</title>
<updated>2016-03-03T01:26:14+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2016-03-03T01:24:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=d2adf941159169a632334686cffa1011f3615779'/>
<id>d2adf941159169a632334686cffa1011f3615779</id>
<content type='text'>
- establish consistent names between existing unconsumed names tests and new ones
added per ref #3666

(cherry picked from commit 6b7c207801d826db872aeda02e7c7b531df68034)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- establish consistent names between existing unconsumed names tests and new ones
added per ref #3666

(cherry picked from commit 6b7c207801d826db872aeda02e7c7b531df68034)
</pre>
</div>
</content>
</entry>
<entry>
<title>Add test for inserting multiple values</title>
<updated>2016-03-03T01:25:59+00:00</updated>
<author>
<name>Athena Yao</name>
<email>athena.yao@cloverhealth.com</email>
</author>
<published>2016-03-02T19:43:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=dfde3b22110827a1dd452ab9a54866792e11891c'/>
<id>dfde3b22110827a1dd452ab9a54866792e11891c</id>
<content type='text'>
(cherry picked from commit a1de176d23ee03724ce269d143790686f862b400)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
(cherry picked from commit a1de176d23ee03724ce269d143790686f862b400)
</pre>
</div>
</content>
</entry>
<entry>
<title>- additional adjustment to the fix made in 8ad968f33100baeb3b13c7e0b724b6b79ab4277f</title>
<updated>2016-02-22T03:46:31+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2016-02-22T03:46:31+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=aa9ce3f521f254da9879ede011e520ec35b8270e'/>
<id>aa9ce3f521f254da9879ede011e520ec35b8270e</id>
<content type='text'>
for ref #3657.  The Oracle dialect makes more use of the "select_wraps_for"
feature than SQL server because Oracle doesn't have "TOP" for a limit-only
select, so tests are showing more happening here.  In the case where
the select() has some dupe columns, these are deduped from the .c collection
so a positional match between the wrapper and original can't use .inner_columns,
because these collections wont match.  Using _columns_plus_names
instead which is the deduped collection that determines the SELECT display,
which definitely have to match up.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
for ref #3657.  The Oracle dialect makes more use of the "select_wraps_for"
feature than SQL server because Oracle doesn't have "TOP" for a limit-only
select, so tests are showing more happening here.  In the case where
the select() has some dupe columns, these are deduped from the .c collection
so a positional match between the wrapper and original can't use .inner_columns,
because these collections wont match.  Using _columns_plus_names
instead which is the deduped collection that determines the SELECT display,
which definitely have to match up.
</pre>
</div>
</content>
</entry>
<entry>
<title>- reworked the way the "select_wraps_for" expression is</title>
<updated>2016-02-21T01:30:58+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2016-02-21T01:22:38+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=cf818984ab52d824dbf77fcb6f18ec4efca53704'/>
<id>cf818984ab52d824dbf77fcb6f18ec4efca53704</id>
<content type='text'>
handled within visit_select(); this attribute was added in the
1.0 series to accommodate the subquery wrapping behavior of
SQL Server and Oracle while also working with positional
column targeting and no longer relying upon "key fallback"
in order to target columns in such a statement.  The IBM DB2
third-party dialect also has this use case, but its implementation
is using regular expressions to rewrite the textual SELECT only
and does not make use of a "wrapped" select at this time.
The logic no longer attempts to reconcile proxy set collections as
this was not deterministic, and instead assumes that the select()
and the wrapper select() match their columns postionally,
at least for the column positions they have in common,
so it is now very simple and safe.  fixes #3657.
- as a side effect of #3657 it was also revealed that the
strategy of calling upon a ResultProxy._getter was not
correctly calling into NoSuchColumnError when an expected
column was not present, and instead returned None up to
loading.instances() to produce NoneType failures; added
a raiseerr argument to _getter() which is called when we
aren't expecting None, fixes #3658.

(cherry picked from commit 8ad968f33100baeb3b13c7e0b724b6b79ab4277f)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
handled within visit_select(); this attribute was added in the
1.0 series to accommodate the subquery wrapping behavior of
SQL Server and Oracle while also working with positional
column targeting and no longer relying upon "key fallback"
in order to target columns in such a statement.  The IBM DB2
third-party dialect also has this use case, but its implementation
is using regular expressions to rewrite the textual SELECT only
and does not make use of a "wrapped" select at this time.
The logic no longer attempts to reconcile proxy set collections as
this was not deterministic, and instead assumes that the select()
and the wrapper select() match their columns postionally,
at least for the column positions they have in common,
so it is now very simple and safe.  fixes #3657.
- as a side effect of #3657 it was also revealed that the
strategy of calling upon a ResultProxy._getter was not
correctly calling into NoSuchColumnError when an expected
column was not present, and instead returned None up to
loading.instances() to produce NoneType failures; added
a raiseerr argument to _getter() which is called when we
aren't expecting None, fixes #3658.

(cherry picked from commit 8ad968f33100baeb3b13c7e0b724b6b79ab4277f)
</pre>
</div>
</content>
</entry>
<entry>
<title>- Fixed bug in :func:`.expression.text` construct where a double-colon</title>
<updated>2016-02-09T23:06:15+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2016-02-09T23:05:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=498b0729b27111130df9b71259e7c8d0299edeea'/>
<id>498b0729b27111130df9b71259e7c8d0299edeea</id>
<content type='text'>
expression would not escape properly, e.g. ``some\:\:expr``, as is most
commonly required when rendering Postgresql-style CAST expressions.
fixes #3644

(cherry picked from commit 29dcaa2b0ae2d26b36ec624be80f56e03ab9095e)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
expression would not escape properly, e.g. ``some\:\:expr``, as is most
commonly required when rendering Postgresql-style CAST expressions.
fixes #3644

(cherry picked from commit 29dcaa2b0ae2d26b36ec624be80f56e03ab9095e)
</pre>
</div>
</content>
</entry>
<entry>
<title>- add literal_binds for delete() statements in addition to insert()/update()</title>
<updated>2016-02-03T16:10:40+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2016-02-03T16:07:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=e2404a4e3fbec54336068be4397e2d8912b9f43c'/>
<id>e2404a4e3fbec54336068be4397e2d8912b9f43c</id>
<content type='text'>
- move tests to CRUDTest
- changelog, fixes #3643

(cherry picked from commit 150591f9e0a94902cb2a76b68ac7c9d8a1a3ec83)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- move tests to CRUDTest
- changelog, fixes #3643

(cherry picked from commit 150591f9e0a94902cb2a76b68ac7c9d8a1a3ec83)
</pre>
</div>
</content>
</entry>
<entry>
<title>fix passing literal_binds flag through for update and insert</title>
<updated>2016-02-03T16:10:38+00:00</updated>
<author>
<name>Tim Tate</name>
<email>timttate@gmail.com</email>
</author>
<published>2016-02-02T23:20:02+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=f87fe4c351316889a70a9dc6145d349dabc3412c'/>
<id>f87fe4c351316889a70a9dc6145d349dabc3412c</id>
<content type='text'>
(cherry picked from commit c9b03fa8afd52646aba8c59fc038330eeee6db60)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
(cherry picked from commit c9b03fa8afd52646aba8c59fc038330eeee6db60)
</pre>
</div>
</content>
</entry>
<entry>
<title>- Fixed issue where inadvertent use of the Python ``__contains__``</title>
<updated>2016-02-02T15:41:01+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2016-02-02T15:15:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/sqlalchemy.git/commit/?id=69f6a8d714c0b1852229bdac05186f2590c5181c'/>
<id>69f6a8d714c0b1852229bdac05186f2590c5181c</id>
<content type='text'>
override with a column expression (e.g. by using ``'x' in col``)
would cause an endless loop in the case of an ARRAY type, as Python
defers this to ``__getitem__`` access which never raises for this
type.  Overall, all use of ``__contains__`` now raises
NotImplementedError.
fixes #3642

(cherry picked from commit e0a580b3d055a600afae61840058a5a30ef5fe74)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
override with a column expression (e.g. by using ``'x' in col``)
would cause an endless loop in the case of an ARRAY type, as Python
defers this to ``__getitem__`` access which never raises for this
type.  Overall, all use of ``__contains__`` now raises
NotImplementedError.
fixes #3642

(cherry picked from commit e0a580b3d055a600afae61840058a5a30ef5fe74)
</pre>
</div>
</content>
</entry>
</feed>
