delta/python-packages/sqlalchemy.git/doc/build/core, branch oracle_numeric github.com: zzzeek/sqlalchemy.git Ensure custom ops have consistent typing behavior, boolean support 2017-09-01T16:34:41+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-09-01T14:35:30+00:00 919b8bc4acf8de4720e8fff5077557f366fb3fb0 Refined the behavior of :meth:`.Operators.op` such that in all cases, if the :paramref:`.Operators.op.is_comparison` flag is set to True, the return type of the resulting expression will be :class:`.Boolean`, and if the flag is False, the return type of the resulting expression will be the same type as that of the left-hand expression, which is the typical default behavior of other operators. Also added a new parameter :paramref:`.Operators.op.return_type` as well as a helper method :meth:`.Operators.bool_op`. Change-Id: Ifc8553cd4037d741b84b70a9702cbd530f1a9de0 Fixes: #4063 
Refined the behavior of :meth:`.Operators.op` such that in all cases,
if the :paramref:`.Operators.op.is_comparison` flag is set to True,
the return type of the resulting expression will be
:class:`.Boolean`, and if the flag is False, the return type of the
resulting expression will be the same type as that of the left-hand
expression, which is the typical default behavior of other operators.
Also added a new parameter :paramref:`.Operators.op.return_type` as well
as a helper method :meth:`.Operators.bool_op`.

Change-Id: Ifc8553cd4037d741b84b70a9702cbd530f1a9de0
Fixes: #4063
include a note about the importance of type coerce for custom ops 2017-09-01T14:52:16+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-09-01T14:52:16+00:00 56845d8cc2678c0aefd889a7fc711150661cd8e8 Change-Id: Ia7dab65523d6a34fcc92ee785ffe03f7e2a33cfd 
Change-Id: Ia7dab65523d6a34fcc92ee785ffe03f7e2a33cfd
- modernize the mysql connection timeout docs 2017-08-22T20:52:10+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-08-22T20:50:19+00:00 2db525614371de011b2c65a41a8b342b15865f3c Change-Id: Icb0474509539c1eb7536544749f2a48b4972078a (cherry picked from commit 4ce46fb0a085c1cc739e21881cc25567e663f8dc) 
Change-Id: Icb0474509539c1eb7536544749f2a48b4972078a
(cherry picked from commit 4ce46fb0a085c1cc739e21881cc25567e663f8dc)
- remove intersphinx usage, the overhead of re-fetching 2017-07-09T17:02:59+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-07-09T17:02:59+00:00 a66979fe1efaa93ba25b1bcd8b67ea2eae2fc48b inventory on every build not worth it Change-Id: I3c4506b246d0f327c4b56afa723975daee984476 
inventory on every build not worth it

Change-Id: I3c4506b246d0f327c4b56afa723975daee984476
Flatten operator precedence for comparison operators 2017-05-25T20:02:13+00:00 Michael Birtwell michael.birtwell@starleaf.com 2017-05-25T15:11:21+00:00 f8a3f14e4f862a4bf0be591699f1f72815c72514 The operator precedence for all comparison operators such as LIKE, IS, IN, MATCH, equals, greater than, less than, etc. has all been merged into one level, so that expressions which make use of these against each other will produce parentheses between them. This suits the stated operator precedence of databases like Oracle, MySQL and others which place all of these operators as equal precedence, as well as Postgresql as of 9.5 which has also flattened its operator precendence. Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Fixes: #3999 Change-Id: I3f3d5124a64af0d376361cdf15a97e2e703be56f Pull-request: https://github.com/zzzeek/sqlalchemy/pull/367 
The operator precedence for all comparison operators such as LIKE, IS,
IN, MATCH, equals, greater than, less than, etc. has all been merged
into one level, so that expressions which make use of these against
each other will produce parentheses between them.   This suits the
stated operator precedence of databases like Oracle, MySQL and others
which place all of these operators as equal precedence, as well as
Postgresql as of 9.5 which has also flattened its operator precendence.

Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Fixes: #3999
Change-Id: I3f3d5124a64af0d376361cdf15a97e2e703be56f
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/367
Repair formatting throughout documentation 2017-05-22T21:53:09+00:00 Kataev Denis kataev@skydns.ru 2017-05-22T21:52:45+00:00 42b6ef8ccd691f6ace30ae16ed70f92e748f763f 1. Section decorators to [one style](http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#sections): without inset at both side and with same length as text. 2. Fix broken [reference](http://docs.sqlalchemy.org/en/latest/core/type_basics.html#generic-types). 3. Convert tabs to space in some small files. 4. Some python code snippets have python+sql syntax hint. Change-Id: I39a7a41ef0b0591c6bf1e610748e2b5c19fc5379 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/361 
1. Section decorators to [one style](http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#sections):
without inset at both side and with same length as text.
2. Fix broken [reference](http://docs.sqlalchemy.org/en/latest/core/type_basics.html#generic-types).
3. Convert tabs to space in some small files.
4. Some python code snippets have python+sql syntax hint.

Change-Id: I39a7a41ef0b0591c6bf1e610748e2b5c19fc5379
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/361
- fix broken link 2017-05-16T13:59:38+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-16T13:59:38+00:00 7aa50b9b197d542b63e86f423865f9bbec7af443 Change-Id: I2f3b5ae29600696b34a6afdddc2f94920febf31d 
Change-Id: I2f3b5ae29600696b34a6afdddc2f94920febf31d
- big rewrite of the Sequence documentation: 2017-05-05T19:05:20+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-05T18:59:39+00:00 654514c5b225f9be80a95b365403ae9fb775804c 1. Sequence should be associated with MetaData always, except in the really weird case someone is sharing a Sequence among multiple metadatas. Make this a "best practice", end the confusion of #3951, #3979 2. "optional" is not a thing people use, trim this way down 3. remove confusing language Change-Id: Iab5aec319da2582092fe2615ee50430f76441aff (cherry picked from commit a1dcf23e371695d8d3be2e1d7875fad10f16a656) 
1. Sequence should be associated with MetaData always,
except in the really weird case someone is sharing a Sequence
among multiple metadatas.  Make this a "best practice", end the
confusion of #3951, #3979

2. "optional" is not a thing people use, trim this way down

3. remove confusing language

Change-Id: Iab5aec319da2582092fe2615ee50430f76441aff
(cherry picked from commit a1dcf23e371695d8d3be2e1d7875fad10f16a656)
Double percent signs based on paramstyle, not dialect 2017-04-05T16:18:36+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-07-04T19:54:29+00:00 86ef507cc73ee4a0a104b334d7ce08ad045e0c76 This patch moves the "doubling" of percent signs into the base compiler and makes it completely a product of whether or not the paramstyle is format/pyformat or not. Without this paramstyle, percent signs are not doubled across text(), literal_column(), and column(). Change-Id: Ie2f278ab1dbb94b5078f85c0096d74dbfa049197 Fixes: #3740 
This patch moves the "doubling" of percent signs into
the base compiler and makes it completely a product
of whether or not the paramstyle is format/pyformat or
not.   Without this paramstyle, percent signs
are not doubled across text(), literal_column(), and
column().

Change-Id: Ie2f278ab1dbb94b5078f85c0096d74dbfa049197
Fixes: #3740
Integrate "pre-ping" into connection pool. 2017-03-20T22:01:23+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-02-24T15:50:14+00:00 f881dae8179b94f72ab0dc85d8f62be8c9ce2fe0 Added native "pessimistic disconnection" handling to the :class:`.Pool` object. The new parameter :paramref:`.Pool.pre_ping`, available from the engine as :paramref:`.create_engine.pool_pre_ping`, applies an efficient form of the "pre-ping" recipe featured in the pooling documentation, which upon each connection check out, emits a simple statement, typically "SELECT 1", to test the connection for liveness. If the existing connection is no longer able to respond to commands, the connection is transparently recycled, and all other connections made prior to the current timestamp are invalidated. Change-Id: I89700d0075e60abd2250e54b9bd14daf03c71c00 Fixes: #3919 
Added native "pessimistic disconnection" handling to the :class:`.Pool`
object.  The new parameter :paramref:`.Pool.pre_ping`, available from
the engine as :paramref:`.create_engine.pool_pre_ping`, applies an
efficient form of the "pre-ping" recipe featured in the pooling
documentation, which upon each connection check out, emits a simple
statement, typically "SELECT 1", to test the connection for liveness.
If the existing connection is no longer able to respond to commands,
the connection is transparently recycled, and all other connections
made prior to the current timestamp are invalidated.

Change-Id: I89700d0075e60abd2250e54b9bd14daf03c71c00
Fixes: #3919