<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/python-packages/sqlalchemy.git/lib/sqlalchemy/testing, branch pr/171</title>
<subtitle>github.com: zzzeek/sqlalchemy.git
</subtitle>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/'/>
<entry>
<title>Mark tests that they require OFFSET support in database</title>
<updated>2015-05-05T14:00:09+00:00</updated>
<author>
<name>Peter Hoffmann</name>
<email>ph@peter-hoffmann.com</email>
</author>
<published>2015-05-05T14:00:09+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=bcc8e6c02b0fd063bf85edc5369899e5717d0232'/>
<id>bcc8e6c02b0fd063bf85edc5369899e5717d0232</id>
<content type='text'>
The sqlalchemy_exasol dialect needs to support Exasol 4.x which does not support 
the OFFSET feature. Mark test with testing.requires.offset so that they can be skipped
of in the exasol specific test suite.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The sqlalchemy_exasol dialect needs to support Exasol 4.x which does not support 
the OFFSET feature. Mark test with testing.requires.offset so that they can be skipped
of in the exasol specific test suite.</pre>
</div>
</content>
</entry>
<entry>
<title>- move away from explicit raises of SkipTest, instead call a</title>
<updated>2015-05-01T17:15:51+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2015-05-01T17:15:51+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=2ef1c56436d25e8a710a8679c59400c0e4009cd6'/>
<id>2ef1c56436d25e8a710a8679c59400c0e4009cd6</id>
<content type='text'>
function patched onto config.  nose/pytest backends now fill
in their exception class here only when loaded
- use more public seeming api to get at py.test Skipped
exception
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
function patched onto config.  nose/pytest backends now fill
in their exception class here only when loaded
- use more public seeming api to get at py.test Skipped
exception
</pre>
</div>
</content>
</entry>
<entry>
<title>- Fixed an import that prevented "pypy setup.py test" from working</title>
<updated>2015-05-01T13:38:21+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2015-05-01T13:38:21+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=088666e8f3de4816b6eeadc2dce0f473b7710bff'/>
<id>088666e8f3de4816b6eeadc2dce0f473b7710bff</id>
<content type='text'>
correctly.
fixes #3406
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
correctly.
fixes #3406
</pre>
</div>
</content>
</entry>
<entry>
<title>- replace old crufty ddl event test fixture with mock</title>
<updated>2015-04-27T19:21:18+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2015-04-27T19:21:18+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=e5c20fce93549d9af972e99a7bf826d7cc99189f'/>
<id>e5c20fce93549d9af972e99a7bf826d7cc99189f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>- Fixed regression regarding the declarative ``__declare_first__``</title>
<updated>2015-04-24T17:49:09+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2015-04-24T17:49:09+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=e73f735382371ac5c05a46f2a51fd10971270fe4'/>
<id>e73f735382371ac5c05a46f2a51fd10971270fe4</id>
<content type='text'>
and ``__declare_last__`` accessors where these would no longer be
called on the superclass of the declarative base.
fixes #3383
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
and ``__declare_last__`` accessors where these would no longer be
called on the superclass of the declarative base.
fixes #3383
</pre>
</div>
</content>
</entry>
<entry>
<title>- repair a regression caused by #3282, where we no longer were</title>
<updated>2015-04-22T18:14:11+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2015-04-22T18:14:11+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=39978060b0d81bd470aade97e608c189b6958dfa'/>
<id>39978060b0d81bd470aade97e608c189b6958dfa</id>
<content type='text'>
applying any topological sort to tables on SQLite.  See the
changelog for details, but we now continue to sort
tables for SQLite on DROP, prohibit the sort from considering
alter, and only warn if we encounter an unresolvable cycle, in
which case, then we forego the ordering.  use_alter as always
is used to break such a cycle.
fixes #3378
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
applying any topological sort to tables on SQLite.  See the
changelog for details, but we now continue to sort
tables for SQLite on DROP, prohibit the sort from considering
alter, and only warn if we encounter an unresolvable cycle, in
which case, then we forego the ordering.  use_alter as always
is used to break such a cycle.
fixes #3378
</pre>
</div>
</content>
</entry>
<entry>
<title>- Fixed a long-standing bug where the :class:`.Enum` type as used</title>
<updated>2015-04-04T16:02:51+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2015-04-04T16:02:51+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=ecd7b31d5eaed138e699293719f70260da3c978d'/>
<id>ecd7b31d5eaed138e699293719f70260da3c978d</id>
<content type='text'>
with the psycopg2 dialect in conjunction with non-ascii values
and ``native_enum=False`` would fail to decode return results properly.
This stemmed from when the PG :class:`.postgresql.ENUM` type used
to be a standalone type without a "non native" option.
fixes #3354
- corrected the assertsql comparison rule to expect a non-ascii
SQL string
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
with the psycopg2 dialect in conjunction with non-ascii values
and ``native_enum=False`` would fail to decode return results properly.
This stemmed from when the PG :class:`.postgresql.ENUM` type used
to be a standalone type without a "non native" option.
fixes #3354
- corrected the assertsql comparison rule to expect a non-ascii
SQL string
</pre>
</div>
</content>
</entry>
<entry>
<title>- fix this for pg8000 of all backends...</title>
<updated>2015-03-24T21:11:22+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2015-03-24T21:11:22+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=4c17337da60b8b126c4a7804f40da236656a1fc8'/>
<id>4c17337da60b8b126c4a7804f40da236656a1fc8</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>- Turned off the "simple order by" flag on the MSSQL dialect; this</title>
<updated>2015-03-24T16:28:19+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2015-03-24T16:28:19+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=86cebccc4c3cfb687cbbe9703cf732641c55ce44'/>
<id>86cebccc4c3cfb687cbbe9703cf732641c55ce44</id>
<content type='text'>
is the flag that per :ticket:`2992` causes an order by or group by
an expression that's also in the columns clause to be copied by
label, even if referenced as the expression object.   The behavior
for MSSQL is now the old behavior that copies the whole expression
in by default, as MSSQL can be picky on these particularly in
GROUP BY expressions.
fixes #3338
- Add a test that includes a composed label in a GROUP BY
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
is the flag that per :ticket:`2992` causes an order by or group by
an expression that's also in the columns clause to be copied by
label, even if referenced as the expression object.   The behavior
for MSSQL is now the old behavior that copies the whole expression
in by default, as MSSQL can be picky on these particularly in
GROUP BY expressions.
fixes #3338
- Add a test that includes a composed label in a GROUP BY
</pre>
</div>
</content>
</entry>
<entry>
<title>- The "auto close" for :class:`.ResultProxy` is now a "soft" close.</title>
<updated>2015-03-17T16:32:33+00:00</updated>
<author>
<name>Mike Bayer</name>
<email>mike_mp@zzzcomputing.com</email>
</author>
<published>2015-03-17T16:32:33+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/python-packages/sqlalchemy.git/commit/?id=b7e151ac5cf5a0c13b9a30bc6841ed0cfe322536'/>
<id>b7e151ac5cf5a0c13b9a30bc6841ed0cfe322536</id>
<content type='text'>
That is, after exhausing all rows using the fetch methods, the
DBAPI cursor is released as before and the object may be safely
discarded, but the fetch methods may continue to be called for which
they will return an end-of-result object (None for fetchone, empty list
for fetchmany and fetchall).   Only if :meth:`.ResultProxy.close`
is called explicitly will these methods raise the "result is closed"
error.
fixes #3330 fixes #3329
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
That is, after exhausing all rows using the fetch methods, the
DBAPI cursor is released as before and the object may be safely
discarded, but the fetch methods may continue to be called for which
they will return an end-of-result object (None for fetchone, empty list
for fetchmany and fetchall).   Only if :meth:`.ResultProxy.close`
is called explicitly will these methods raise the "result is closed"
error.
fixes #3330 fixes #3329
</pre>
</div>
</content>
</entry>
</feed>
