summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Added missing text_type requirement to TextTestpr/82Stefan Reich2014-03-261-0/+2
|
* - Fixed regression caused by release 0.8.5 / 0.9.3's compatibilityMike Bayer2014-03-253-2/+17
| | | | | | | | | enhancements where index reflection on Postgresql versions specific to only the 8.1, 8.2 series again broke, surrounding the ever problematic int2vector type. While int2vector supports array operations as of 8.1, apparently it only supports CAST to a varchar as of 8.3. fix #3000
* - Fixed regression from 0.8.3 as a result of :ticket:`2818`Mike Bayer2014-03-223-1/+28
| | | | | | where :meth:`.Query.exists` wouldn't work on a query that only had a :meth:`.Query.select_from` entry but no other entities. re: #2818 fixes #2995
* - Adjusted ``setup.py`` file to support the possible futureMike Bayer2014-03-223-22/+74
| | | | | | | | | | | | | | | | | | | | | | | removal of the ``setuptools.Feature`` extension from setuptools. If this keyword isn't present, the setup will still succeed with setuptools rather than falling back to distutils. C extension building can be disabled now also by setting the DISABLE_SQLALCHEMY_CEXT environment variable. This variable works whether or not setuptools is even available. fixes #2986 - using platform.python_implementation() in setup.py to detect CPython. I've tested this function on OSX and linux on Python 2.6 through 3.4, including 3.1, 3.2, 3.3. Unfortunately, on OSX + 3.2 only, it seems to segfault. I've tried installing 3.2.5 from the python.org .dmg, building it from source, and also blew away the whole 3.2 directory, something seems to be wrong with the "platform" module on that platform only, and there's also no issue on bugs.python.org; however, I'm going with it anyway. If someone is using 3.2 on OSX they really should be upgrading. - adjusted the logic for platform_implementation(), apparently "platform" is there in python 2.5, so we are doing a version check. Conflicts: doc/build/intro.rst setup.py
* - reword the paragraph which talks about web framework integration for sessions:Mike Bayer2014-03-201-10/+7
| | | | | | | | | | | 1. fix the typo in the paragraph, fixes #2998 2. as zope-sqlalchemy only provides transaction integration and not session scoping, dial back the language here as people are probably using scoped_session with pyramid anyway 3. as I'm going to again start recommending people don't cling to flask-sqlalchemy so hard, take out the word "strongly" from the recommendation. 4. as flask is the only framework I can think of that actually has an explicit SQLAlchemy layer that handles setting up scoped_session, take out the word "most", now it's "some web frameworks" (by which it means "only flask...and flask-sqlalchemy is probably not worth using anyway")
* fix assertionMike Bayer2014-03-191-1/+1
|
* - Fixed bug in mutable extension as well asMike Bayer2014-03-196-3/+43
| | | | | | | | | | :func:`.attributes.flag_modified` where the change event would not be propagated if the attribute had been reassigned to itself. fixes #2997 Conflicts: lib/sqlalchemy/orm/state.py test/orm/test_attributes.py
* Add is_ and isnot filter to the tutorialCharles-Axel Dein2014-03-171-0/+6
| | | | Most linter complain when comparing with None.
* - Improved an error message which would occur if a query() were madeMike Bayer2014-03-173-0/+29
| | | | | | | against a non-selectable, such as a :func:`.literal_column`, and then an attempt was made to use :meth:`.Query.join` such that the "left" side would be determined as ``None`` and then fail. This condition is now detected explicitly.
* typoMike Bayer2014-03-161-1/+1
|
* - fairly epic rework of the cascade documentationMike Bayer2014-03-155-172/+337
| | | | | Conflicts: lib/sqlalchemy/orm/relationships.py
* Merge pull request #79 from nibrahim/mastermike bayer2014-03-111-1/+1
| | | | Fixes argument number in docs
* merge new links to rel_0_8Mike Bayer2014-03-091-12/+5
|
* cut out the BS as far as MySQLdb urls, put the one url everyone should be usingMike Bayer2014-03-041-22/+14
|
* - Fixed bug in :func:`.tuple_` construct where the "type" of essentiallyMike Bayer2014-02-273-6/+62
| | | | | | | | | | | | | | | the first SQL expression would be applied as the "comparison type" to a compared tuple value; this has the effect in some cases of an inappropriate "type coersion" occurring, such as when a tuple that has a mix of String and Binary values improperly coerces target values to Binary even though that's not what they are on the left side. :func:`.tuple_` now expects heterogeneous types within its list of values. fixes #2977 Conflicts: lib/sqlalchemy/sql/elements.py test/sql/test_operators.py
* 0.8.6Mike Bayer2014-02-261-1/+1
|
* - Removed stale names from ``sqlalchemy.orm.interfaces.__all__`` andMike Bayer2014-02-262-4/+16
| | | | | | refreshed with current names, so that an ``import *`` from this module again works. fixes #2975
* 0.8.5rel_0_8_5Mike Bayer2014-02-193-3/+4
|
* 2014Mike Bayer2014-02-19134-135/+135
|
* - isolate this failure as only on 0.8, only in py3.3, just comment it out,Mike Bayer2014-02-191-1/+9
| | | | not really worth tracking down
* - Added an additional message to psycopg2 disconnect detection,Mike Bayer2014-02-192-0/+10
| | | | | | "could not send data to server", which complements the existing "could not receive data from server" and has been observed by users, fixes #2936
* - add a topological rule here to place PARTITIONS after PARTITION_BY,Mike Bayer2014-02-191-1/+2
| | | | for output consistency within the tests as well as in practice
* restore check ahead of the lock to avoid locking when not neededMike Bayer2014-02-191-6/+7
|
* - add improved support here for string parsing of predicates, backportMike Bayer2014-02-191-1/+8
| | | | from 0.9
* - Support has been improved for Postgresql reflection behavior on very oldMike Bayer2014-02-196-29/+54
| | | | | | | | | | | | | | | | (pre 8.1) versions of Postgresql, and potentially other PG engines such as Redshift (assuming Redshift reports the version as < 8.1). The query for "indexes" as well as "primary keys" relies upon inspecting a so-called "int2vector" datatype, which refuses to coerce to an array prior to 8.1 causing failures regarding the "ANY()" operator used in the query. Extensive googling has located the very hacky, but recommended-by-PG-core-developer query to use when PG version < 8.1 is in use, so index and primary key constraint reflection now work on these versions. Conflicts: doc/build/changelog/changelog_09.rst test/dialect/postgresql/test_types.py
* - Added new MySQL-specific :class:`.mysql.DATETIME` which includesMike Bayer2014-02-193-20/+108
| | | | | | | fractional seconds support; also added fractional seconds support to :class:`.mysql.TIMESTAMP`. DBAPI support is limited, though fractional seconds are known to be supported by MySQL Connector/Python. Patch courtesy Geert JM Vanderkelen. #2941
* changelog for pullreq 12Mike Bayer2014-02-191-0/+11
|
* Fixes MySQL dialect partitioningMarcus McCurdy2014-02-192-2/+32
|
* - Fixed bug where calling :meth:`.Insert.values` with an empty listMike Bayer2014-02-193-0/+33
| | | | | | | | or tuple would raise an IndexError. It now produces an empty insert construct as would be the case with an empty dictionary. Conflicts: lib/sqlalchemy/sql/dml.py
* - Fixed a critical regression caused by :ticket:`2880` where the newlyMike Bayer2014-02-193-3/+61
| | | | | | | | | concurrent ability to return connections from the pool means that the "first_connect" event is now no longer synchronized either, thus leading to dialect mis-configurations under even minimal concurrency situations. Conflicts: lib/sqlalchemy/event/attr.py
* - update mysql connector python link, #2938Mike Bayer2014-02-181-1/+1
|
* - changelog for pullreq github:72.Mike Bayer2014-02-161-0/+9
|
* Merge branch 'fix_sqlite_uc_reflection' of ↵Mike Bayer2014-02-162-1/+5
|\ | | | | | | https://github.com/malor/sqlalchemy into t
| * Fix unique constraints reflection in SQLitepr/72Roman Podoliaka2014-02-142-1/+5
| | | | | | | | | | | | | | | | | | Reflection of unique constraints didn't work properly, if reserved identifiers had been used as column names. In this case column names would be put in double quotes (e.g. the name of column asc would be returned as "asc"). This issue is only present in 0.8.4 and not in 0.9.x.
* | - extensive cross-linking of relationship options with their documentation ↵Mike Bayer2014-02-168-234/+428
| | | | | | | | | | | | | | | | | | | | | | sections - convert all paramter references in relationship documentation to :paramref: Conflicts: doc/build/orm/relationships.rst lib/sqlalchemy/ext/declarative/__init__.py lib/sqlalchemy/orm/relationships.py
* | - add cross-linking for passive_deletes / passive_updatesMike Bayer2014-02-163-13/+22
| |
* | - add documentation regarding native hstore flag, psycopg2Mike Bayer2014-02-161-4/+31
| | | | | | | | hstore extension. #2959
* | - expand docs on MySQL table arguments beyond just storage enginesMike Bayer2014-02-151-30/+63
| | | | | | | | | | - clarify section on "foreign key reflection" and group this in a section that refers to foreign keys.
* | - Revised this very old issue where the Postgresql "get primary key"Mike Bayer2014-02-142-1/+25
|/ | | | | | | reflection query were updated to take into account primary key constraints that were renamed; the newer query fails on very old versions of Postgresql such as version 7, so the old query is restored in those cases when server_version_info < (8, 0) is detected. #2291
* - Fixed bug where :meth:`.in_()` would go into an endless loop ifMike Bayer2014-02-133-2/+49
| | | | | | erroneously passed a column expression whose comparator included the ``__getitem__()`` method, such as a column that uses the :class:`.postgresql.ARRAY` type. [ticket:2957]
* this example doesn't work, we don't really have a solution for this as far ↵Mike Bayer2014-02-101-31/+0
| | | | as automating this pattern
* - dont need these extra conditions from the previous testMike Bayer2014-02-101-5/+0
|
* - Fixed bug where :meth:`.Query.get` would fail to consistentlyMike Bayer2014-02-103-4/+39
| | | | | | raise the :class:`.InvalidRequestError` that invokes when called on a query with existing criterion, when the given identity is already present in the identity map. [ticket:2951]
* - this seems to be the best string for pymysqlMike Bayer2014-02-031-1/+1
|
* - Fixed bug which prevented MySQLdb-based dialects (e.g.Mike Bayer2014-02-034-32/+29
| | | | | | | | | | pymysql) from working in Py3K, where a check for "connection charset" would fail due to Py3K's more strict value comparison rules. The call in question wasn't taking the database version into account in any case as the server version was still None at that point, so the method overall has been simplified to rely upon connection.character_set_name(). [ticket:2933]
* - add a few missing methods to the cymysql dialectMike Bayer2014-02-022-0/+17
|
* - don't duplicate docs for Pool within QueuePoolMike Bayer2014-01-311-70/+68
| | | | - add huge warning regarding how use_threadlocal probably not what you want
* changelogMike Bayer2014-01-311-0/+9
|
* no Binary here if we are running a test with no DBAPIMike Bayer2014-01-311-0/+2
|
* Merge branch 'fix-convenience-import' of github.com:witsch/sqlalchemy into tMike Bayer2014-01-311-1/+1
|\
View Lorry Controller Status