summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix issue with unbaking subqueriespr/290Mark Hahnenberg2016-07-122-13/+23
| | | | | We were improperly capturing a loop variable inside a lambda during unbaking, which would cause us to load incorrect data when executing queries.
* Update index.rstpr/289Shige Takeda2016-07-111-1/+1
|
* Update index.rstShige Takeda2016-07-111-0/+1
|
* - fix typoMike Bayer2016-07-071-1/+1
| | | | Change-Id: Ie66d419a5188529a64fcb2e2463c15c26863889f
* Add additional documentation re: JSONEncodedDictMike Bayer2016-07-071-15/+92
| | | | | | | | | Add an example of how to use coerce_compared_value() specific to JSONEncodedDict, as this example class is frequently dropped into applications. Change-Id: I61639ac03dc5a37673ee8201b99a3c36ab944f00 Fixes: #3742
* - 1.0.14 changelog updateMike Bayer2016-07-061-0/+1
| | | | | | (cherry picked from commit e9a1d7bc6a0ae4ec09b6431d23d201654013c6a7) Change-Id: I5bab3fd6f2ec4986fd6b1049844f3851958d0c66
* Merge "Adapt "FOR UPDATE OF" with Oracle limit/offset"mike bayer2016-07-063-3/+106
|\
| * Adapt "FOR UPDATE OF" with Oracle limit/offsetMike Bayer2016-07-053-3/+106
| | | | | | | | | | | | | | | | | | | | 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
* | `index_property` catches IndexError as well as KeyErrorJeong YunWon2016-07-053-3/+11
|/ | | | | | | It was raising AttributeError for key accessing in dict, but raising IndexError for index accessing in array. Change-Id: I58a2252a9e8d7f78cabcefcbe7223a4f3a729115
* - version bumpMike Bayer2016-07-052-1/+4
| | | | Change-Id: I5ace1a90f36678c006d704b452fbbe8a3eb1cd0a
* Repair PG BIGSERIAL w/ TypeDecorator, VariantMike Bayer2016-07-043-1/+33
| | | | | | | | | | | | | Some of the dialect impl memoization for TypeDecorator necessarily keeps the top-level TypeDecorator type around, since a user-defined type will have bind and result set processing behavior. For both TypeDecorator and Variant, PG dialect needs to ensure it's looking at the SQLAlchemy type to check for SmallInteger / BigInteger. Fixes: 3739 Change-Id: I2d45fb997f17c6272d6bb826a77d2dba665adae7 (cherry picked from commit 421fa6b8bf9f0c3c5041579c89ec405ce0f5e0b0)
* Merge remote-tracking branch 'origin/pr/288'Mike Bayer2016-07-041-1/+1
|\
| * fixed typopr/288Kristian Perkins2016-07-031-1/+1
| |
* | Fix some typos in 1.1's changelog and migration sectionspr/287Lele Gaifax2016-07-022-18/+18
| |
* | Consistently use the official PostgreSQL casingLele Gaifax2016-07-023-45/+45
|/
* - add backportsMike Bayer2016-07-011-0/+2
| | | | | Change-Id: Iee0bf9e60a5991bedbe29b305803b4c79ac5c511 (cherry picked from commit 849df799ec4107d0992c8eb0e015b74916aee266)
* Preserve type for math negationMike Bayer2016-07-013-1/+16
| | | | | | | | | | Fixed issue in SQL math negation operator where the type of the expression would no longer be the numeric type of the original. This would cause issues where the type determined result set behaviors. Change-Id: If0e339614a3686e251235fc94b6f59310c4630a5 Fixes: #3735
* - 1.1.0b2rel_1_1_0b2Mike Bayer2016-07-012-2/+3
|
* - revert the RTD reqs workaround, we are self-hosting nowMike Bayer2016-07-011-31/+0
| | | | Change-Id: Ie11361147d497c6eb6418cdc850ed277dfbd1de4
* Merge "Repair pickling for Properties object"mike bayer2016-06-293-2/+47
|\
| * Repair pickling for Properties objectPieter Mulder2016-06-293-2/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | Fixed bug whereby the ``__getstate__`` / ``__setstate__`` methods for sqlalchemy.util.Properties were non-working due to the transition in the 1.0 series to ``__slots__``. The issue potentially impacted some third-party applications. Pull request courtesy Pieter Mulder. Fixes: #3728 Change-Id: I01ebd425bbfe145747fea2edd0d2d412c74fd84d Pull-request: https://github.com/zzzeek/sqlalchemy/pull/286 (cherry picked from commit cab57e9bab04fbdea44690c08dff379a29eaab32)
* | Ensure @compiles calls down to the original compilation schemeMike Bayer2016-06-293-6/+76
|/ | | | | | | | | | | | | | | Made a slight behavioral change in the ``sqlalchemy.ext.compiler`` extension, whereby the existing compilation schemes for an established construct would be removed if that construct was itself didn't already have its own dedicated ``__visit_name__``. This was a rare occurrence in 1.0, however in 1.1 :class:`.postgresql.ARRAY` subclasses :class:`.sqltypes.ARRAY` and has this behavior. As a result, setting up a compilation handler for another dialect such as SQLite would render the main :class:`.postgresql.ARRAY` object no longer compilable. Fixes: #3732 Change-Id: If2c1ada4eeb09157885888e41f529173902f2b49
* Make boolean processors consistent between Py/C; coerce to 1/0Mike Bayer2016-06-236-14/+152
| | | | | | | | | | | | | The processing performed by the :class:`.Boolean` datatype for backends that only feature integer types has been made consistent between the pure Python and C-extension versions, in that the C-extension version will accept any integer value from the database as a boolean, not just zero and one; additionally, non-boolean integer values being sent to the database are coerced to exactly zero or one, instead of being passed as the original integer value. Change-Id: I01e647547fd7047bd549dd70e1fa202c51e8328b Fixes: #3730
* Don't reorder PrimaryKeyConstraint columns if explicitMike Bayer2016-06-205-3/+49
| | | | | | | | | | | Dialed back the "order the primary key columns per auto-increment" described in :ref:`change_mysql_3216` a bit, so that if the :class:`.PrimaryKeyConstraint` is explicitly defined, the order of columns is maintained exactly, allowing control of this behavior when necessary. Change-Id: I9e7902c57a96c15968a6abf53e319acf15680da0 Fixes: #3726
* Disable Enum string validation by defaultMike Bayer2016-06-206-18/+115
| | | | | | | | | | | | | | Rolled back the validation rules a bit in :class:`.Enum` to allow unknown string values to pass through, unless the flag ``validate_string=True`` is passed to the Enum; any other kind of object is still of course rejected. While the immediate use is to allow comparisons to enums with LIKE, the fact that this use exists indicates there may be more unknown-string-comparsion use cases than we expected, which hints that perhaps there are some unknown string-INSERT cases too. Change-Id: I7d1d79b374a7d47966d410998f77cd19294ab7b0 Fixes: #3725
* - create space for 1.1.0b2Mike Bayer2016-06-202-1/+4
| | | | Change-Id: I8815a68dcf6e5d27f3f82b02f939f72d9a412337
* - update alembic linkMike Bayer2016-06-183-3/+3
| | | | Change-Id: I5ac6ba8234873fdd19bee6c1decd311a9cb4d55e
* - missing indexable.rstMike Bayer2016-06-181-0/+13
| | | | Change-Id: Ida3ca92b496a1e3ebd761c100201d3660460c2bf
* 1.1.0b1Mike Bayer2016-06-162-1/+2
|
* - dont need thisMike Bayer2016-06-161-13/+2
|
* Merge "Add DDLCompiler.create_table_suffix()"mike bayer2016-06-163-1/+35
|\
| * Add DDLCompiler.create_table_suffix()Mark Sandan2016-06-163-1/+35
| | | | | | | | | | | | | | Allows custom dialects to add keywords after the CREATE TABLE section. Change-Id: I6fa66dfcf00ef95122f491a9115410df2746cf88
* | Merge "update pytest good practices link in PyTest class"mike bayer2016-06-161-2/+4
|\ \ | |/ |/|
| * update pytest good practices link in PyTest classMark Sandan2016-06-161-2/+4
| | | | | | | | | | Change-Id: Ie96edd05e962663e9ddeeda85b24858caabd3bfd Pull-request: https://github.com/zzzeek/sqlalchemy/pull/262
* | - dont use id() to test identity as these can be recycledMike Bayer2016-06-151-12/+14
| | | | | | | | Change-Id: Ie4cb4924909d55c5962f66e36cd5325e8e8f0538
* | - flake8Mike Bayer2016-06-151-106/+128
| | | | | | | | Change-Id: I74e369d1d71c98cb0af58dde80b7d535d17cbdf7
* | Merge "Add TABLESAMPLE clause support."mike bayer2016-06-159-2/+206
|\ \
| * | Add TABLESAMPLE clause support.saarni2016-06-159-2/+206
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The TABLESAMPLE clause allows randomly selecting an approximate percentage of rows from a table. At least DB2, Microsoft SQL Server and recent Postgresql support this standard clause. Fixes: #3718 Change-Id: I3fb8b9223e12a57100df30876b461884c58d72fa Pull-request: https://github.com/zzzeek/sqlalchemy/pull/277
* | | Merge "Interpret lateral, alias as from clauses"mike bayer2016-06-152-2/+4
|\ \ \ | |/ / |/| |
| * | Interpret lateral, alias as from clausesMike Bayer2016-06-152-2/+4
| | | | | | | | | | | | | | | | | | Also add doc members for Lateral. Change-Id: Ic801c296377ce84230139c6a43ecb3e93a852832
* | | Add `sqlalchemy.ext.index` for indexed attributes for ORMJeong YunWon2016-06-158-1/+724
|/ / | | | | | | | | | | | | | | | | Add `sqlalchemy.ext.index.index_property` which subscribe an index of a column with `Indexable` type. Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Change-Id: I238c23131e4fded5dc7f7a25eb02e26008099d00 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/235
* | Merge "Add ON CONFLICT support for Postgresql"mike bayer2016-06-1410-15/+1102
|\ \
| * | Add ON CONFLICT support for PostgresqlRobin Thomas2016-06-1410-15/+1102
| | | | | | | | | | | | | | | | | | | | | Fixes: #3529 Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Change-Id: Ie3bf6ad70d9be9f0e44938830e922db03573991a Pull-request: https://github.com/zzzeek/sqlalchemy/pull/258
* | | Deprecate FromClause.count()Mike Bayer2016-06-1421-141/+193
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | count() here is misleading in that it not only counts from an arbitrary column in the table, it also does not make accommodations for DISTINCT, JOIN, etc. as the ORM-level function does. Core should not be attempting to provide a function like this. Change-Id: I9916fc51ef744389a92c54660ab08e9695b8afc2 Fixes: #3724
* | | Ensure CTE internals are handled during cloneMike Bayer2016-06-103-0/+34
|/ / | | | | | | | | | | | | | | | | The CTE construct was missing a _copy_internals() method which would handle CTE-specific structures including _cte_alias, _restates during a clone operation. Change-Id: I9aeac9cd24d8f7ae6b70e52650d61f7c96cb6d7e Fixes: #3722
* | Support `postgresql_concurrently` on index dropping.Iuri de Silvio2016-06-083-5/+73
| | | | | | | | | | | | | | | | | | | | | | | | Also adds version detection so that DROP INDEX CONCURRENTLY only renders if the Postgresql version is 9.2 or higher; for CREATE INDEX CONCURRENTLY, version detection is added to allow the phrase to omit if the Postgresql version is less than 8.2. Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Change-Id: I597287e0ebbbe256c957a3579b58ace6848ab4f4 Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/84
* | Merge "Support normal /materialized views in PG separately"mike bayer2016-06-084-3/+81
|\ \
| * | Support normal /materialized views in PG separatelySebastian Bank2016-06-064-3/+81
| | | | | | | | | | | | | | | | | | Fixes: #3588 Change-Id: Ifbfcab67375f289ddb5c4522f4b803cb8b7c34de Pull-request: https://github.com/zzzeek/sqlalchemy/pull/250
* | | Use the "committed" values when extracting many-to-one lazyload valueMike Bayer2016-06-084-17/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The scalar object set() method calls upon the lazy loader to get at the "old" value of the attriute, however doesn't ensure that the "committed" value of the foreign key attributes is used. If the user has manipulated these attributes and they themselves have pending, non committed changes, we get the "new" value which these attributes would have set up if they were flushed. "old" vs "new" value is always about how the value has changed since the load, so we always have to use the DB-persisted values for everything when looking for "old". Change-Id: I82bdc40ad0cf033c3a98f3361776cf3161542cd6 Fixes: #3708
* | | Merge "Add 'FOR NO KEY UPDATE' / 'FOR KEY SHARE' support for Postgresql"mike bayer2016-06-088-17/+141
|\ \ \
View Lorry Controller Status