summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* new docstring for Query.group_bypr/297Iuri Diniz2016-07-291-1/+6
| | | | Instructions how to suppress GROUP BY.
* Allow suppressing GROUP BY by passing NoneIuri Diniz2016-07-291-0/+5
|
* tests for cancellation of group_by (passing None)Iuri Diniz2016-07-291-0/+14
|
* test: append something to group_by (ORM)Iuri Diniz2016-07-291-0/+7
|
* Missing test for group_by (ORM)Iuri Diniz2016-07-291-0/+11
|
* - Document how SQL Server does MAX with VARCHAR, NVARCHARMike Bayer2016-07-271-0/+20
| | | | | | Fixes #3760 Change-Id: I0613eb66bfdc9d7118688c74e29c8da322c3b4db
* - 1.1.0b3rel_1_1_0b3Mike Bayer2016-07-262-2/+3
|
* Allow Table._reset_exported to silently passMike Bayer2016-07-244-2/+28
| | | | | | | | | | | Fixed bug in :class:`.Table` where the internal method ``_reset_exported()`` would corrupt the state of the object. This method is intended for selectable objects and is called by the ORM in some cases; an erroneous mapper configuration would could lead the ORM to call this on on a :class:`.Table` object. Change-Id: I63fa34ee0cdf16358bb125c556390df79758bcbc Fixes: #3755
* - MySQL's JSON shared implementation completely w/ sqltypes.JSON;Mike Bayer2016-07-242-38/+3
| | | | | | | | | | this must have been an oversight. Leave mysql.JSON in place still as we might need to add things to it. - CAST(json, String) still confusing MySQL drivers even mysqlclient. Since here we're checking for the raw form of the JSON and not a typical round trip, add a force for unicode Change-Id: I727f4526a01a0875037cf0dede45cd074da5205a
* - don't use pymysql at all for JSON, there's Py2K failures alsoMike Bayer2016-07-241-1/+1
| | | | Change-Id: I39a574ea72f5c7af0084dee3169679c5f534cb8b
* - Workaround in tests for https://github.com/PyMySQL/PyMySQL/issues/488Mike Bayer2016-07-241-4/+6
| | | | Change-Id: I4f935cce878eb1678b432f4cb4ba6ee122f8e9d4
* - a variety of test adjustments to accomodate for MySQL 5.7Mike Bayer2016-07-248-17/+46
| | | | Change-Id: Ied4245433d0d7b469dae6e7394c4931d8405f387
* Remove same-named relationship warningMike Bayer2016-07-194-12/+125
| | | | | | | | | | Removed a warning that dates back to 0.4 which emits when a same-named relationship is placed on two mappers that inherits via joined or single table inheritance. The warning does not apply to the current unit of work implementation. Change-Id: If528ec3a2f4dc60712d9044fd1ec6c4dfbf0eadb Fixes: #3749
* - fix formattingMike Bayer2016-07-181-3/+3
| | | | Change-Id: Ieba940a998a6aa287864e9748c2995ee4ae5bf54
* Merge "Add `default` parameter for `index_property`"mike bayer2016-07-133-4/+62
|\
| * Add `default` parameter for `index_property`Jeong YunWon2016-07-113-4/+62
| | | | | | | | | | | | And force to use keyword arguments for trivial parameters in index_property Change-Id: I12a178128182f77a2d06b52d7e36f59a36b45a33
* | Ensure DML provides named_with_column for CTE(Alias)Mike Bayer2016-07-133-0/+41
| | | | | | | | | | | | | | | | | | | | | | | | Fixed bug in new CTE feature for update/insert/delete whereby an anoymous (e.g. no name passed) :class:`.CTE` construct around the statement would fail. The Alias base class of CTE checks for the "named_with_column" attribute in order to detect if the underlying selectable has a name; UpdateBase now provides this as False. Change-Id: I4b0309db21379a4c0cb93085298c86da3cf840e4 Fixes: #3744
* | Merge "Work w/ prefetch even for selects, if present"mike bayer2016-07-136-34/+170
|\ \
| * | Work w/ prefetch even for selects, if presentMike Bayer2016-07-126-34/+170
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed bug in new CTE feature for update/insert/delete stated as a CTE inside of an enclosing statement (typically SELECT) whereby oninsert and onupdate values weren't called upon for the embedded statement. This is accomplished by consulting prefetch for all statements. The collection is also broken into separate insert/update collections so that we don't need to consult toplevel self.isinsert to determine if the prefetch is for an insert or an update. What we don't yet test for are CTE combinations that have both insert/update in one statement, though these should now work in theory provided the underlying database supports such a statement. Change-Id: I3b6a860e22c86743c91c56a7ec751ff706f66f64 Fixes: #3745
* | | Fix issue with unbaking subqueriesMark Hahnenberg2016-07-123-13/+32
|/ / | | | | | | | | | | | | | | | | | | Fix improper capture of a loop variable inside a lambda during unbaking of subquery eager loaders, which would cause the incorrect query to be invoked. Fixes: #3743 Change-Id: I995110deb8ee2dae8540486729e1ae64578d28fc Pull-request: https://github.com/zzzeek/sqlalchemy/pull/290
* | - 1.0.15 for devMike Bayer2016-07-121-0/+3
| | | | | | | | Change-Id: I2d75b6d9ca533e662bc8160cf5fc52355e5e549e
* | 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
|
View Lorry Controller Status