summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* dialects/mysql: inspect superclass for IntegerType in __repr__pr/53pr/52Haydn Dufrene2013-12-171-0/+4
| | | | This was causing issues with Alembic (https://bitbucket.org/zzzeek/alembic/issue/127/auto-generate-seems-to-miss-unsigned)
* Merge branch 'rel_0_8' of /Users/classic/dev/sqlalchemy into rel_0_8rel_0_8_4Mike Bayer2013-12-081-1/+1
|\
| * forgot authors!!Mike Bayer2013-12-081-1/+1
| |
* | 0.8.4 prepMike Bayer2013-12-082-2/+3
|/
* python2.5 fixMike Bayer2013-12-081-1/+1
|
* - documentation cleanup in ORM including [ticket:2816]Mike Bayer2013-12-073-35/+80
| | | | | Conflicts: lib/sqlalchemy/orm/mapper.py
* specify run as module hereMike Bayer2013-12-071-5/+6
|
* - remove verbiage about "namespaces" from the dogpile example, [ticket:2862]Mike Bayer2013-12-073-20/+23
| | | | - fix broken py2k/py3k isms
* - A DBAPI that raises an error on ``connect()`` which is not a subclassMike Bayer2013-12-074-15/+68
| | | | | | | | | | | | of dbapi.Error (such as ``TypeError``, ``NotImplementedError``, etc.) will propagate the exception unchanged. Previously, the error handling specific to the ``connect()`` routine would both inappropriately run the exception through the dialect's :meth:`.Dialect.is_disconnect` routine as well as wrap it in a :class:`sqlalchemy.exc.DBAPIError`. It is now propagated unchanged in the same way as occurs within the execute process. [ticket:2881] - add tests for this in test_parseconnect, but also add tests in test_execute to ensure the execute() behavior as well
* - restore having the connection closed before decrementing the overflow counterMike Bayer2013-12-061-2/+4
|
* - The :class:`.QueuePool` has been enhanced to not block new connectionMike Bayer2013-12-063-31/+126
| | | | | | | | attempts when an existing connection attempt is blocking. Previously, the production of new connections was serialized within the block that monitored overflow; the overflow counter is now altered within it's own critical section outside of the connection process itself. [ticket:2880]
* - Made a slight adjustment to the logic which waits for a pooledMike Bayer2013-12-063-8/+36
| | | | | | | | | | | connection to be available, such that for a connection pool with no timeout specified, it will every half a second break out of the wait to check for the so-called "abort" flag, which allows the waiter to break out in case the whole connection pool was dumped; normally the waiter should break out due to a notify_all() but it's possible this notify_all() is missed in very slim cases. This is an extension of logic first introduced in 0.8.0, and the issue has only been observed occasionally in stress tests.
* - changelog + test for pullreq #7, MSSQL dialect for DROP INDEXMike Bayer2013-12-052-0/+22
|
* Fix MSSQL dialects visit_drop_index to use the correct DDLdonkopotamus2013-12-051-5/+3
|
* fix for 2.5Mike Bayer2013-12-041-1/+1
|
* - move tests for unique constraints to dialect suite, includingMike Bayer2013-12-034-35/+57
| | | | requirements etc., just like 0.9
* - backport unique constraints reflection to 0.8.4, therebyRoman Podolyaka2013-12-037-5/+147
| | | | | | | | | | | | | | | assisting with alembic installations that have upgraded and are dealing with PG index/unique constraint reflection. 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 ORA-02396 "maximum idle time" error code to list ofMike Bayer2013-12-032-1/+10
| | | | "is disconnect" codes with cx_oracle. [ticket:2864]
* - the pronoun removal commit. there was only one instance of aMike Bayer2013-11-307-20/+23
| | | | | | | | standalone gendered pronoun with a gender-neutral subject, but also have replaced all occurences of "his/her", "his or her", etc. The docs have always strived to account for both genders in any non-specific singular pronoun, however recent controversy in the community suggests that a zero-gendered-pronoun policy is probably best going forward.
* - reduce verbiage in mutation.py regarding legacy style, place under ↵Mike Bayer2013-11-293-10/+11
| | | | | | | versionadded Conflicts: lib/sqlalchemy/ext/mutable.py
* Merge pull request #47 from yoloseem/patch-2mike bayer2013-11-291-1/+1
|\ | | | | Fixed a syntax error in example code.
| * Fixed a syntax error in example code.pr/47Hyunjun Kim2013-11-211-1/+1
| |
* | -be more agnostic of quotes hereMike Bayer2013-11-231-2/+2
| | | | | | | | | | Conflicts: test/engine/test_execute.py
* | - Fixed bug where SQL statement would be improperly ASCII-encodedMike Bayer2013-11-224-3/+33
| | | | | | | | | | | | | | | | | | | | when a pre-DBAPI :class:`.StatementError` were raised within :meth:`.Connection.execute`, causing encoding errors for non-ASCII statements. The stringification now remains within Python unicode thus avoiding encoding errors. [ticket:2871] Conflicts: test/engine/test_execute.py
* | Fixed bug where Oracle ``VARCHAR`` types given with no lengthMike Bayer2013-11-223-1/+18
| | | | | | | | | | (e.g. for a ``CAST`` or similar) would incorrectly render ``None CHAR`` or similar. [ticket:2870]
* | - cleanupMike Bayer2013-11-221-274/+288
| |
* | disable this test for py3k, this is better fixed in 0.9Mike Bayer2013-11-211-6/+7
| |
* | py3k fix for non-ascii SQL stringsMike Bayer2013-11-211-2/+3
| |
* | - Fixed bug which prevented the ``serializer`` extension from workingMike Bayer2013-11-214-11/+40
| | | | | | | | | | | | | | | | | | | | correctly with table or column names that contain non-ASCII characters. [ticket:2869] Conflicts: lib/sqlalchemy/ext/serializer.py lib/sqlalchemy/sql/selectable.py lib/sqlalchemy/testing/assertions.py
* | - add a sanity-check test for repr(), comparing against what we getMike Bayer2013-11-211-1/+13
|/ | | | in 0.9 for [ticket:2868]
* - apply a timeout to all join() calls for test_poolMike Bayer2013-11-171-5/+10
| | | | | | | - use thread.join() for waiters_handled test Conflicts: test/engine/test_pool.py
* sync up some changes for #2604 and #2607 from 0.7.10, 0.8.0b2Mike Bayer2013-11-142-20/+21
|
* sync up the 07/08 changelogs from masterMike Bayer2013-11-142-89/+82
|
* add start-line here to avoid RST parse errorsMike Bayer2013-11-141-0/+1
|
* Fix cross referencesVraj Mohan2013-11-145-14/+15
|
* Add undocumented members to resolve cross referencesVraj Mohan2013-11-141-0/+1
|
* Ensure API generationVraj Mohan2013-11-141-0/+3
|
* Ensure API generation and fix cross referencesVraj Mohan2013-11-143-2/+37
|
* Ensure API doc for make_url and resolve referencesVraj Mohan2013-11-143-3/+5
|
* Suppress warnings about files not being included in any toctreeVraj Mohan2013-11-145-0/+10
|
* Fix indentation and escape *args and **kwargsVraj Mohan2013-11-142-3/+3
|
* Fix indentation and escape *args and **kwargsVraj Mohan2013-11-129-119/+124
|
* add sap sqlanywhereMike Bayer2013-11-121-0/+1
|
* css updates to better work with RTD badgeMike Bayer2013-11-112-2/+17
|
* - add a section re: using column_reflect for mapping, link to it from the ↵Mike Bayer2013-10-312-10/+51
| | | | "naming columns distinctly" and "column_prefix" sections since this is often what ppl are looking for. [ticket:2856] is related.
* - Fixed a regression introduced by :ticket:`2818` where the EXISTSMike Bayer2013-10-303-5/+27
| | | | | | query being generated would produce a "columns being replaced" warning for a statement with two same-named columns, as the internal SELECT wouldn't have use_labels set.
* merge the same fix from masterMike Bayer2013-10-281-1/+1
|
* no such thing as default_strategy()...Mike Bayer2013-10-281-2/+3
|
* fix to the changelog system for when there's no change recs in the bodyMike Bayer2013-10-271-1/+5
|
* - Fixed bug where index reflection would mis-interpret indkey valuesMike Bayer2013-10-273-2/+17
| | | | | | | | | | when using the pypostgresql adapter, which returns these values as lists vs. psycopg2's return type of string. [ticket:2855] Conflicts: doc/build/changelog/changelog_09.rst lib/sqlalchemy/__init__.py