summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* - Fixed bug where the combination of "limit" rendering askonsta_3022Mike Bayer2014-04-304-15/+60
| | | | | | | | | "SELECT FIRST n ROWS" using a bound parameter (only firebird has both), combined with column-level subqueries which also feature "limit" as well as "positional" bound parameters (e.g. qmark style) would erroneously assign the subquery-level positions before that of the enclosing SELECT, thus returning parameters which are out of order. Fixes #3038
* - move test_propagate to test/orm/inheritance as the propagate flag isMike Bayer2014-04-188-133/+142
| | | | | | | | | | | | | specific to mapper inheritance - tweak Proxy property to give the proxied descriptor a chance to raise an exception - have Concrete prop raise on all access, not just trying to use it in a query. This might be a little problematic backwards compatible-wise, however - adjust mapper and relationship to more correctly allow for concreteinheritedprop to be overridden, in the case of backrefs etc., some cases were still raising due to how props are set up - work assert_raises/assert_raises_message to be expressed via a context manager that can be used directly
* Merge branch 'feature/3022-propagate-option-for-relationship' of ↵Mike Bayer2014-04-188-25/+179
|\ | | | | | | bitbucket.org:kvesteri/sqlalchemy into konsta_3022
| * Add propagate flag for relationshipKonsta Vesterinen2014-04-188-25/+179
| |
* | - Revised the query used to determine the current default schema nameMike Bayer2014-04-172-14/+18
| | | | | | | | | | | | | | to use the ``database_principal_id()`` function in conjunction with the ``sys.database_principals`` view so that we can determine the default schema independently of the type of login in progress (e.g., SQL Server, Windows, etc). fixes #3025
* | - Fixed bug in new :meth:`.DialectKWArgs.argument_for` method whereMike Bayer2014-04-153-0/+21
|/ | | | | adding an argument for a construct not previously included for any special arguments would fail. fixes #3024
* changelogMike Bayer2014-04-141-0/+9
|
* Merged in goodscloud/sqlalchemy (pull request #14) Mike Bayer2014-04-144-6/+15
|\ | | | | fixes for #2830
| * use importlib.machinery to load modules instead of imp under Python 3.3 and ↵Matt Chisholm2014-04-142-4/+13
| | | | | | | | | | | | greater part of #2830
| * remove unused importMatt Chisholm2014-04-141-1/+0
| |
| * fix unclosed file ResourceWarningMatt Chisholm2014-04-141-1/+2
|/ | | | part of #2830
* - Added a new "disconnect" message "connection has been closed unexpectedly".Mike Bayer2014-04-111-0/+12
| | | | | This appears to be related to newer versions of SSL. Pull request courtesy Antti Haapala.
* Merged in ↵Mike Bayer2014-04-111-1/+3
|\ | | | | | | | | | | antti_haapala/sqlalchemy/antti_haapala/added-an-ssl-related-connection-error-1397245079299 (pull request #13) added an SSL related connection error
| * added an SSL related connection errorantti_haapala2014-04-111-1/+3
|/
* Merge pull request #84 from Daniel-B-Smith/mastermike bayer2014-04-111-1/+1
|\ | | | | Fixed bug in example code on orm session page.
| * Fixed bug in example code.pr/84Daniel Smith2014-04-101-1/+1
| |
* | - Fixed regression introduced in 0.9 where new "ORDER BY <labelname>"Mike Bayer2014-04-103-1/+18
|/ | | | | | feature from :ticket:`1068` would not apply quoting rules to the label name as rendered in the ORDER BY. fix #3020, re: #1068
* - Added new utility function :func:`.make_transient_to_detached` which canMike Bayer2014-04-095-3/+95
| | | | | | | be used to manufacture objects that behave as though they were loaded from a session, then detached. Attributes that aren't present are marked as expired, and the object can be added to a Session where it will act like a persistent one. fix #3017
* repair erroneous whitespace in autodoc directives, preventing members fromMike Bayer2014-04-061-8/+0
| | | | being documented
* - Restored the import for :class:`.Function` to the ↵Mike Bayer2014-04-052-1/+7
| | | | | | ``sqlalchemy.sql.expression`` import namespace, which was removed at the beginning of 0.9.
* - add some docs for the instancestate linkage to the inspection systemMike Bayer2014-04-042-5/+89
|
* escape backslashMike Bayer2014-04-021-1/+1
|
* - reverse order of columns in sample CTEs as this is a UNION and the cols ↵Mike Bayer2014-04-023-9/+7
| | | | | | | | | | need to line up - alter this in the unit tests as well as these queries were just copied from the tests - remove the included_parts.join(parts) from the core CTE doc (also just copied from the test, where we want to make sure joins don't get screwed up with the CTE) as it doesn't contribute to the query itself fixes #3014
* - back off the callcounts a bit for the boolean fixMike Bayer2014-04-012-20/+23
| | | | - rewrite callcounts for select()
* - Fixes to the newly enhanced boolean coercion in :ticket:`2804` whereMike Bayer2014-04-015-7/+95
| | | | | | | the new rules for "where" and "having" woudn't take effect for the "whereclause" and "having" kw arguments of the :func:`.select` construct, which is also what :class:`.Query` uses so wasn't working in the ORM either. fixes #3013 re: #2804
* - Added new flag :paramref:`.expression.between.symmetric`, when set to TrueMike Bayer2014-03-307-13/+93
| | | | | | | renders "BETWEEN SYMMETRIC". Also added a new negation operator "notbetween_op", which now allows an expression like ``~col.between(x, y)`` to render as "col NOT BETWEEN x AND y", rather than a parentheiszed NOT string. fixes #2990
* updateMike Bayer2014-03-301-1/+1
|
* - fix mapper refMike Bayer2014-03-282-4/+1
| | | | - don't talk about "can't check for rows matched" here as we changed that in 0.9
* 0.9.4rel_0_9_4Mike Bayer2014-03-283-2/+4
|
* dont need rowcount here...Mike Bayer2014-03-281-1/+0
|
* - Added new parameter :paramref:`.mapper.confirm_deleted_rows`. DefaultsMike Bayer2014-03-285-29/+80
| | | | | | | | | | | | to True, indicates that a series of DELETE statements should confirm that the cursor rowcount matches the number of primary keys that should have matched; this behavior had been taken off in most cases (except when version_id is used) to support the unusual edge case of self-referential ON DELETE CASCADE; to accomodate this, the message is now just a warning, not an exception, and the flag can be used to indicate a mapping that expects self-refererntial cascaded deletes of this nature. See also :ticket:`2403` for background on the original change. re: #2403 fix #3007
* - revert part of c01558ae7f4a for now as we also test that a DELETE of two rowsMike Bayer2014-03-284-15/+26
| | | | | | where one is to be deleted from ON DELETE CASCADE succeeds; the check here makes that fail. We will need to add an option to enable/disable this check per mapping, will likely do this in next version
* mark failing tests for buggy mysqlconnectorMike Bayer2014-03-281-0/+21
|
* revert inadvertent pdbMike Bayer2014-03-281-2/+0
|
* - the rewording of orderinglist docs got committed by accident, finish it upMike Bayer2014-03-281-20/+12
|
* - add further coverage for join_condition to make sure we get this case whereMike Bayer2014-03-282-1/+11
| | | | there are multiple, equivalent foreign keys
* pickle of execption not supported on mysqlconnectorMike Bayer2014-03-281-0/+2
|
* - fix set syntax supposed to be dictMike Bayer2014-03-281-1/+1
|
* - Fixed ORM bug where changing the primary key of an object, then markingMike Bayer2014-03-2810-37/+183
| | | | | | | | | | | | | it for DELETE would fail to target the correct row for DELETE. Then to compound matters, basic "number of rows matched" checks were not being performed. Both issues are fixed, however note that the "rows matched" check requires so-called "sane multi-row count" functionality; the DBAPI's executemany() method must count up the rows matched by individual statements and SQLAlchemy's dialect must mark this feature as supported, currently applies to some mysql dialects, psycopg2, sqlite only. fixes #3006 - Enabled "sane multi-row count" checking for the psycopg2 DBAPI, as this seems to be supported as of psycopg2 2.0.9.
* clarify doc hereMike Bayer2014-03-281-4/+4
|
* - fix py3k bug re: dictionary values(), fixes #3005Mike Bayer2014-03-281-1/+1
|
* - Added support to automap for the case where a relationship shouldMike Bayer2014-03-283-14/+93
| | | | | | | not be created between two classes that are in a joined inheritance relationship, for those foreign keys that link the subclass back to the superclass. fixes #3004
* - Fixed a very old behavior where the lazy load emitted for a one-to-manyMike Bayer2014-03-274-7/+191
| | | | | | | | | | | | | | | | | could inappropriately pull in the parent table, and also return results inconsistent based on what's in the parent table, when the primaryjoin includes some kind of discriminator against the parent table, such as ``and_(parent.id == child.parent_id, parent.deleted == False)``. While this primaryjoin doesn't make that much sense for a one-to-many, it is slightly more common when applied to the many-to-one side, and the one-to-many comes as a result of a backref. Loading rows from ``child`` in this case would keep ``parent.deleted == False`` as is within the query, thereby yanking it into the FROM clause and doing a cartesian product. The new behavior will now substitute the value of the local "parent.deleted" for that parameter as is appropriate. Though typically, a real-world app probably wants to use a different primaryjoin for the o2m side in any case. fixes #2948
* - Improved the check for "how to join from A to B" such that whenMike Bayer2014-03-273-16/+82
| | | | | | | | | a table has multiple, composite foreign keys targeting a parent table, the :paramref:`.relationship.foreign_keys` argument will be properly interpreted in order to resolve the ambiguity; previously this condition would raise that there were multiple FK paths when in fact the foreign_keys argument should be establishing which one is expected. fixes #2965
* - Tweaked the settings for mysql-connector-python; in Py2K, theMike Bayer2014-03-277-14/+38
| | | | | | | | | | | "supports unicode statements" flag is now False, so that SQLAlchemy will encode the *SQL string* (note: *not* the parameters) to bytes before sending to the database. This seems to allow all unicode-related tests to pass for mysql-connector, including those that use non-ascii table/column names, as well as some tests for the TEXT type using unicode under cursor.executemany(). - other mysql-connector fixes; latest version seems to do better on function call counts
* Added missing text_type requirement to TextTestStefan Reich2014-03-271-0/+1
| | | | | Conflicts: lib/sqlalchemy/testing/suite/test_types.py
* - fixes to multi-backend testsMike Bayer2014-03-274-15/+133
| | | | | - move the logic to determine "test id" into plugin_base - update callcounts
* fixes to get profiling tests working againMike Bayer2014-03-263-6/+8
|
* dont warn, that just crashes the test...Mike Bayer2014-03-261-2/+3
|
* try to liberalize the pool._refs assertion a bitMike Bayer2014-03-261-2/+34
|
View Lorry Controller Status