summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Tidy range types docs and add warning about the return type support offered ↵pr/12Chris Withers2013-06-261-2/+18
| | | | by different versions of different DBAPI libraries.
* Fix NameError in example.Chris Withers2013-06-261-4/+1
|
* YEAR(2) emits a warning and oursql / mysqlconnector throw an exceptionMike Bayer2013-06-231-4/+2
| | | | on the warning so just dump it
* docsMike Bayer2013-06-233-9/+105
|
* doc fixesMike Bayer2013-06-231-5/+6
|
* 0.8 changelogMike Bayer2013-06-232-1/+10
|
* 0.9 changelogMike Bayer2013-06-231-0/+9
|
* - add a test for pullreq 8Mike Bayer2013-06-232-3/+29
| | | | - simplify
* Merge branch 'master' of https://github.com/asldevi/sqlalchemy into some_branchMike Bayer2013-06-231-1/+2
|\
| * make tests passpr/8Devi2013-06-201-1/+1
| |
| * check if compostite_class is of class typeDevi2013-06-191-1/+2
| | | | | | | | before checking if it is a subclass of `MutableComposite`
* | sort here so that exception messages are testableMike Bayer2013-06-231-1/+1
| |
* | tweak this for now, would need a testMike Bayer2013-06-232-14/+3
| |
* | The resolution of :class:`.ForeignKey` objects to theirMike Bayer2013-06-236-147/+580
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | target :class:`.Column` has been reworked to be as immediate as possible, based on the moment that the target :class:`.Column` is associated with the same :class:`.MetaData` as this :class:`.ForeignKey`, rather than waiting for the first time a join is constructed, or similar. This along with other improvements allows earlier detection of some foreign key configuration issues. Also included here is a rework of the type-propagation system, so that it should be reliable now to set the type as ``None`` on any :class:`.Column` that refers to another via :class:`.ForeignKey` - the type will be copied from the target column as soon as that other column is associated, and now works for composite foreign keys as well. [ticket:1765]
* | ticket #1443 is for unique constraint reflectionMike Bayer2013-06-231-0/+1
| |
* | Merge pull request #11 from malor/fix_uc_reflectionmike bayer2013-06-233-13/+26
|\ \ | | | | | | Fix unique constraints reflection in SQLite and PostgreSQL
| * | Fix unique constraints reflection in PostgreSQLpr/11Roman Podolyaka2013-06-232-11/+18
| | | | | | | | | | | | Reflection of unique constraints must preserve the order of columns.
| * | Fix unique constraints reflection in SQLiteRoman Podolyaka2013-06-232-1/+6
| | | | | | | | | | | | | | | | | | | | | If SQLite keywords are used as column names, they are quoted. The code parsing the information about table unique constraints should be modified so that it properly removes double-quotes from column names.
| * | Improve _test_get_unique_constraints()Roman Podolyaka2013-06-231-1/+2
| | | | | | | | | | | | | | | | | | Call eq_() in a loop instead of comparing two lists directly. This makes it much easier to find out which element is not equal to the reference value.
* | | Merge pull request #10 from malor/fix_unicode_literalsmike bayer2013-06-232-9/+10
|\ \ \ | |/ / |/| | Fix unicode literals on Python 3.1 and 3.2
| * | 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
| |
View Lorry Controller Status