summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix unicode literals on Python 3.1 and 3.2pr/10Roman Podolyaka2013-06-232-9/+10
| | | | | A few tests use u'' unicode literals which are not supported in Python versions 3.1 and 3.2.
* Provided a new attribute for :class:`.TypeDecorator`Mike Bayer2013-06-225-4/+95
| | | | | | | | | called :attr:`.TypeDecorator.coerce_to_is_types`, to make it easier to control how comparisons using ``==`` or ``!=`` to ``None`` and boolean types goes about producing an ``IS`` expression, or a plain equality expression with a bound parameter. [ticket:2744]
* versionaddsMike Bayer2013-06-221-6/+33
|
* 0.9 changelogMike Bayer2013-06-221-0/+8
|
* - 0.8 changelogMike Bayer2013-06-222-11/+19
| | | | - some whitespace
* this locale is not needed. maybe it is somewhere but the locale I have ↵Mike Bayer2013-06-222-18/+9
| | | | | | ("C", whatever that means, cannot find meaning of this anywhere in Postgresql documentation) seems to work
* Merge pull request #5 from cjw296/pg-rangesmike bayer2013-06-227-4/+640
|\ | | | | Support for Postgres range types.
| * Documentation for the new range type support.pr/5Chris Withers2013-06-104-7/+69
| |
| * Implement EXCLUDE constraints for postgres.Chris Withers2013-06-104-1/+139
| |
| * add support for range operators listed in ↵Chris Withers2013-06-102-7/+234
| | | | | | | | http://www.postgresql.org/docs/9.2/interactive/functions-range.html
| * Basic type support for the new range types in postgres 9.2Chris Withers2013-06-105-2/+211
| |
* | Merged in goodscloud/sqlalchemy (pull request #3) Mike Bayer2013-06-181-0/+3
|\ \ | | | | | | Forgot final check that a delete in a backref also doesn't create a new version
| * | Forgot final check that a delete in a backref also doesn't create a new versionMatt Chisholm2013-06-171-0/+3
| | | | | | | | | | | | follow up to https://bitbucket.org/zzzeek/sqlalchemy/pull-request/2
* | | fix up the isolation level docs which were a messMike Bayer2013-06-172-25/+58
| | |
* | | remove double methodsMike Bayer2013-06-171-19/+0
| | |
* | | turn this requirement back down as the simpler serialize works better nowMike Bayer2013-06-172-8/+1
| | |
* | | - rework PropComparator.adapted() to be PropComparator.adapt_to_entity(),Mike Bayer2013-06-177-122/+139
| | | | | | | | | | | | | | | | | | | | | passes in AliasedInsp and allows more flexibility. - rework the AliasedClass/AliasedInsp relationship so that AliasedInsp has all state and functionality. AliasedClass is just a facade. [ticket:2756]
* | | migration for [ticket:2751]Mike Bayer2013-06-172-1/+98
| | |
* | | changelog for 0.8Mike Bayer2013-06-171-0/+8
| | |
* | | changelogMike Bayer2013-06-171-0/+8
| | |
* | | Merge branch 'master' of bitbucket.org:zzzeek/sqlalchemyMike Bayer2013-06-172-3/+42
|\ \ \ | |/ /
| * | Merged in goodscloud/sqlalchemy (pull request #2) Mike Bayer2013-06-172-3/+42
| |\ \ | | | | | | | | don't create a history entry when an object in a backref has changed
| | * | don't create a history entry when an object in a backref has changedMatt Chisholm2013-06-152-3/+42
| | | | | | | | | | | | | | | | The code that determines whether an object in a relation has been added/removed does not take into account that that relation may be a backref. If the relation is a backref, then nothing on the current table is changing, and therefore no history entry should be created.
* | | | can remove this, issue is fixedMike Bayer2013-06-171-10/+1
|/ / /
* | | - clean up this test (really we don't even need this, it's not testing much)Mike Bayer2013-06-161-13/+20
| | | | | | | | | | | | | | | - for the moment, put a catch in it to see if we can trap that issue on jenkins
* | | - changelogMike Bayer2013-06-154-3/+25
| | | | | | | | | | | | - docs
* | | Merge pull request #7 from malor/psycopg2_execution_optionsmike bayer2013-06-152-0/+11
|\ \ \ | | | | | | | | Add AUTOCOMMIT isolation level support for psycopg2
| * | | Add AUTOCOMMIT isolation level support for psycopg2pr/7Roman Podolyaka2013-06-152-0/+11
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | One can use this to emit statements, which can not be executed within a transaction (e. g. CREATE DATABASE): from sqlalchemy import create_engine eng = create_engine('postgresql://test:test@localhost/test') conn = eng.connect().execution_options(isolation_level='AUTOCOMMIT') conn.execute('CREATE DATABASE test2;') Fixes issue #2072.
* | | Fixed bug in polymorphic SQL generation where multiple joined-inheritanceMike Bayer2013-06-154-6/+119
|/ / | | | | | | | | | | | | entities against the same base class joined to each other as well would not track columns on the base table independently of each other if the string of joins were more than two entities long. Also in 0.8.2. [ticket:2759]
* | - skip this test for py3k. serializer kind of a bustMike Bayer2013-06-142-1/+9
| |
* | changelog for thisMike Bayer2013-06-101-1/+36
| |
* | changelogMike Bayer2013-06-102-0/+16
| |
* | Merge pull request #6 from eevee/propagate-reset-on-returnmike bayer2013-06-102-1/+5
|\ \ | | | | | | Preserve reset_on_return when recreating a Pool.
| * | Preserve reset_on_return when recreating a Pool.pr/6Eevee2013-06-102-1/+5
|/ /
* | Fixed bug where sending a composite attribute into :meth:`.Query.order_by`Mike Bayer2013-06-104-2/+42
| | | | | | | | | | would produce a parenthesized expression not accepted by some databases. [ticket:2754]
* | Fixed the interaction between composite attributes andMike Bayer2013-06-105-19/+78
|/ | | | | | the :func:`.aliased` function. Previously, composite attributes wouldn't work correctly in comparison operations when aliasing was applied. Also in 0.8.2. [ticket:2755]
* this comment is ancientMike Bayer2013-06-091-5/+0
|
* these notes about **kw are incorrect, we are talking about the return value hereMike Bayer2013-06-091-8/+0
|
* - get_unique_constraints() pull requestMike Bayer2013-06-097-35/+68
| | | | | | - version (0.9 for now) - changelog - move the test into the test suite so that all dialects can take advantage of it
* Merge pull request #4 from malor/reflect_constraintsmike bayer2013-06-096-0/+141
|\ | | | | Add basic support of unique constraints reflection
| * Add basic support of unique constraints reflectionpr/4Roman Podolyaka2013-06-096-0/+141
| | | | | | | | | | | | | | | | | | | | | | | | Inspection API already supports reflection of table indexes information and those also include unique constraints (at least for PostgreSQL and MySQL). But it could be actually useful to distinguish between indexes and plain unique constraints (though both are implemented in the same way internally in RDBMS). This change adds a new method to Inspection API - get_unique_constraints() and implements it for SQLite, PostgreSQL and MySQL dialects.
* | Added pool logging for "rollback-on-return" and the less usedMike Bayer2013-06-092-6/+21
|/ | | | | | "commit-on-return". This is enabled with the rest of pool "debug" logging. [ticket:2752]
* ...and...its a behavioral improvementMike Bayer2013-06-081-92/+88
|
* fix this exampleMike Bayer2013-06-081-2/+2
|
* mention right joins, make it clear we're talking about left outer join as ↵Mike Bayer2013-06-081-5/+13
| | | | the bigger issue
* oracle 9 does support this, oracle 8 is a special case.Mike Bayer2013-06-081-5/+6
|
* cleanupMike Bayer2013-06-082-15/+6
|
* get nested joins to render on oracle 8Mike Bayer2013-06-082-3/+43
|
* - tests for the alias() APIMike Bayer2013-06-084-42/+379
| | | | - docs docs docs
* formattingMike Bayer2013-06-081-3/+3
|
View Lorry Controller Status