summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* fix mysql+cymysql dialectpr/61Hajime Nakagami2014-01-251-0/+8
|
* Merge branch 'cymysql' of github.com:nakagami/sqlalchemy into cymysqlHajime Nakagami2014-01-240-0/+0
|\
| * Merge branch 'master' into cymysqlHajime Nakagami2013-10-27187-5509/+12552
| |\
| * \ Merge branch 'master' into cymysqlHajime Nakagami2013-08-18124-18410/+20877
| |\ \
* | \ \ Merge branch 'master' into cymysqlHajime Nakagami2014-01-24404-28211/+46643
|\ \ \ \ | |/ / / |/| | | | | | | | | | | Conflicts: lib/sqlalchemy/util/__init__.py
| * | | - doc updates, include links to create_engine from tutorials, cleanupMike Bayer2014-01-235-60/+103
| | | | | | | | | | | | | | | | and modernize the engines chapter a bit
| * | | typoMike Bayer2014-01-231-3/+5
| | | |
| * | | - remove this leftover commented pdbMike Bayer2014-01-231-5/+0
| | | |
| * | | - Fixed an 0.9 regression where the automatic aliasing applied byMike Bayer2014-01-235-3/+82
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | :class:`.Query` and in other situations where selects or joins were aliased (such as joined table inheritance) could fail if a user-defined :class:`.Column` subclass were used in the expression. In this case, the subclass would fail to propagate ORM-specific "annotations" along needed by the adaptation. The "expression annotations" system has been corrected to account for this case. [ticket:2918]
| * | | Merge pull request #60 from wichert/mutable-doc-importmike bayer2014-01-231-1/+0
| |\ \ \ | | | | | | | | | | Remove uneeded import from code example
| | * | | Remove uneeded import from code examplepr/60Wichert Akkerman2014-01-201-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | This had me reread the code twice to see if I missed why the import was present.
| * | | | used the wrong joinMike Bayer2014-01-221-5/+2
| | | | |
| * | | | - Support is improved for supplying a :func:`.join` construct as theMike Bayer2014-01-2211-18/+459
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | target of :paramref:`.relationship.secondary` for the purposes of creating very complex :func:`.relationship` join conditions. The change includes adjustments to query joining, joined eager loading to not render a SELECT subquery, changes to lazy loading such that the "secondary" target is properly included in the SELECT, and changes to declarative to better support specification of a join() object with classes as targets.
| * | | | - Added new test coverage for so-called "down adaptions" of SQL types,Mike Bayer2014-01-224-11/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | where a more specific type is adapted to a more generic one - this use case is needed by some third party tools such as ``sqlacodegen``. The specific cases that needed repair within this test suite were that of :class:`.mysql.ENUM` being downcast into a :class:`.types.Enum`, and that of SQLite date types being cast into generic date types. The ``adapt()`` method needed to become more specific here to counteract the removal of a "catch all" ``**kwargs`` collection on the base :class:`.TypeEngine` class that was removed in 0.9. [ticket:2917]
| * | | | - add redshift-sqlalchemy, essentially fixes [ticket:2727]Mike Bayer2014-01-211-0/+2
| | | | |
| * | | | - update docs for Numeric/Float, in particular warn against using mismatchedMike Bayer2014-01-211-32/+41
| | | | | | | | | | | | | | | | | | | | types (e.g. [ticket:2916])
| * | | | - Fixed the multiple-table "UPDATE..FROM" construct, only usable onMike Bayer2014-01-205-51/+270
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MySQL, to correctly render the SET clause among multiple columns with the same name across tables. This also changes the name used for the bound parameter in the SET clause to "<tablename>_<colname>" for the non-primary table only; as this parameter is typically specified using the :class:`.Column` object directly this should not have an impact on applications. The fix takes effect for both :meth:`.Table.update` as well as :meth:`.Query.update` in the ORM. [ticket:2912]
| * | | | use new paramlinks 0.2.2, trying to fix param links for __init__ vs. classMike Bayer2014-01-201-1/+1
| | | | |
| * | | | - further refine this so that the ordering of columns is maintained asMike Bayer2014-01-202-16/+18
| | | | | | | | | | | | | | | | | | | | | | | | | sent to the primary key constraint; existing tests in the PG dialect confirm this.
| * | | | - simplify the mechanics of PrimaryKeyConstraint with regards to reflection;Mike Bayer2014-01-207-25/+267
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | reflection now updates the PKC in place. - support the use case of the empty PrimaryKeyConstraint in order to specify constraint options; the columns marked as primary_key=True will now be gathered into the columns collection, rather than being ignored. [ticket:2910] - add validation such that column specification should only take place in the PrimaryKeyConstraint directly, or by using primary_key=True flags; if both are present, they have to match exactly, otherwise the condition is assumed to be ambiguous, and a warning is emitted; the old behavior of using the PKC columns only is maintained.
| * | | | - repair signature for base get_unique_constraints() methodMike Bayer2014-01-202-1/+2
| | | | | | | | | | | | | | | | | | | | - test_autoincrement_col still needs reflection overall
| * | | | - ensure ordering is fully maintained, [ticket:2914]Mike Bayer2014-01-202-6/+9
| |/ / /
| * | | fix typoMike Bayer2014-01-191-1/+1
| | | |
| * | | Merge pull request #59 from wichert/doc-relationship-typomike bayer2014-01-191-1/+1
| |\ \ \ | | | | | | | | | | Fix a typo in the relationship docs
| | * | | Fix a typo in the relationship docspr/59Wichert Akkerman2014-01-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The text refers to ``boston_addresses``, while the code sample uses ``addresses``.
| * | | | - alter behavior such that dialect_kwargs is still immutable, butMike Bayer2014-01-192-28/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | now represents exactly the kwargs that were passed, and not the defaults. the defaults are still in dialect_options. This allows repr() schemes such as that of alembic to not need to look through and compare for defaults.
| * | | | - some test fixesMike Bayer2014-01-194-41/+33
| | | | | | | | | | | | | | | | | | | | - clean up some shenanigans in reflection
| * | | | akiban-> foundationdbMike Bayer2014-01-181-3/+2
| | | | |
| * | | | - implement kwarg validation and type system for dialect-specificMike Bayer2014-01-1816-81/+562
| | | | | | | | | | | | | | | | | | | | | | | | | arguments; [ticket:2866] - add dialect specific kwarg functionality to ForeignKeyConstraint, ForeignKey
| * | | | credit to Derek HarlandMike Bayer2014-01-181-0/+1
| | | | |
| * | | | - changelog for pullreq:11Mike Bayer2014-01-182-1/+17
| | | | | | | | | | | | | | | | | | | | - be specific about version 0.9.2
| * | | | Merge branch 'patch-msql-pkc-clustered' of bitbucket.org:dharland/sqlalchemy ↵Mike Bayer2014-01-184-8/+118
| |\ \ \ \ | | | | | | | | | | | | | | | | | | into m
| | * | | | Bug Fix: Stop generating bad sql if an empty UniqueConstraint() is givendonkopotamus2014-01-173-0/+26
| | | | | |
| | * | | | Support mssql_clustered option on UniqueConstraint (plus docs and test)donkopotamus2014-01-172-4/+41
| | | | | |
| | * | | | Remove support for mssql_clustered on Tabledonkopotamus2014-01-172-27/+6
| | | | | |
| | * | | | Support mssql_clustered option in mssql dialect for both Table and ↵donkopotamus2014-01-142-8/+76
| | | | | | | | | | | | | | | | | | | | | | | | PrimaryKeyConstraint
| | * | | | Merged zzzeek/sqlalchemy into masterDerek Harland2014-01-14228-1345/+5913
| | |\ \ \ \
| * | | | | | cx_oracle is now "conditional" on py2kMike Bayer2014-01-171-3/+5
| | | | | | |
| * | | | | | - rework Oracle to no longer do its own unicode conversion; this has been ↵Mike Bayer2014-01-175-17/+104
| | |_|/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | observed to be very slow. this now has the effect of producing "conditional" unicode conversion for the Oracle backend, as it still returns NVARCHAR etc. as unicode [ticket:2911] - add new "conditional" functionality to unicode processors; the C-level function now uses PyUnicode_Check() as a fast alternative to the isinstance() check in Python
| * | | | | even simplerMike Bayer2014-01-151-8/+4
| | | | | |
| * | | | | - should close the session before rolling back the transactionMike Bayer2014-01-151-3/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - make section title actually say, "such as for test suites" - add topic section detailing an evented approach to allowing ROLLBACK by using savepoint
| * | | | | - changelog + test for pullreq github 58Mike Bayer2014-01-142-0/+16
| | | | | |
| * | | | | Merge pull request #58 from kstark/patch-1mike bayer2014-01-141-1/+1
| |\ \ \ \ \ | | | | | | | | | | | | | | Fix TypeError for class_mapper called w/ iterable
| | * | | | | Fix TypeError for class_mapper called w/ iterablepr/58Kyle Stark2014-01-131-1/+1
| | | | | | | | | | | | | | | | | | | | | When the class_ passed is not a mapped class but is actually an iterable, the string formatting operation fails with a TypeError, and the expected ArgumentError is not raised. Calling code which is using reflection and expects this error will fail (e.g. the sadisplay module).
| * | | | | | - _cursor_execute() will close the cursor on error; oracle doesn't allow ↵Mike Bayer2014-01-132-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | double close - ensure no iterator changed size issues in testing.engines
| * | | | | | - Fixed a bug involving the new flattened JOIN structures whichMike Bayer2014-01-133-4/+151
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | are used with :func:`.joinedload()` (thereby causing a regression in joined eager loading) as well as :func:`.aliased` in conjunction with the ``flat=True`` flag and joined-table inheritance; basically multiple joins across a "parent JOIN sub" entity using different paths to get to a target class wouldn't form the correct ON conditions. An adjustment / simplification made in the mechanics of figuring out the "left side" of the join in the case of an aliased, joined-inh class repairs the issue. [ticket:2908]
| * | | | | | - a little bit of profile bump, just on insert not too concernedMike Bayer2014-01-131-3/+3
| | |_|/ / / | |/| | | |
| * | | | | - The MySQL CAST compilation now takes into account aspects of a stringMike Bayer2014-01-138-34/+121
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | type such as "charset" and "collation". While MySQL wants all character- based CAST calls to use the CHAR type, we now create a real CHAR object at CAST time and copy over all the parameters it has, so that an expression like ``cast(x, mysql.TEXT(charset='utf8'))`` will render ``CAST(t.col AS CHAR CHARACTER SET utf8)``. - Added new "unicode returns" detection to the MySQL dialect and to the default dialect system overall, such that any dialect can add extra "tests" to the on-first-connect "does this DBAPI return unicode directly?" detection. In this case, we are adding a check specifically against the "utf8" encoding with an explicit "utf8_bin" collation type (after checking that this collation is available) to test for some buggy unicode behavior observed with MySQLdb version 1.2.3. While MySQLdb has resolved this issue as of 1.2.4, the check here should guard against regressions. The change also allows the "unicode" checks to log in the engine logs, which was not previously the case. [ticket:2906]
| * | | | update changelog from 0.3.2 to 0.3.4, re-patching the part of ↵Mike Bayer2014-01-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2775c95b1ee30831216cc5 that was intended
| * | | | revert r2775c95b1ee30831216cc5 which was mostly an inadvertent commit, ↵Mike Bayer2014-01-134-44/+23
| | | | | | | | | | | | | | | | | | | | except for the changelog part