summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* fix typo in cascade documentationpr/127Michael White2014-08-051-1/+1
|
* - Fixed bug in CTE where ``literal_binds`` compiler argument would notMike Bayer2014-08-021-0/+9
| | | | | | be always be correctly propagated when one CTE referred to another aliased CTE in a statement. Fixes #3154
* - update the literal binds sectionMike Bayer2014-07-301-43/+24
|
* - The exception wrapping system for DBAPI errors can now accommodateMike Bayer2014-07-291-0/+11
| | | | | | | | non-standard DBAPI exceptions, such as the psycopg2 TransactionRollbackError. These exceptions will now be raised using the closest available subclass in ``sqlalchemy.exc``, in the case of TransactionRollbackError, ``sqlalchemy.exc.OperationalError``. fixes #3075
* - Fixed 0.9.7 regression caused by :ticket:`3067` in conjunction withMike Bayer2014-07-291-0/+9
| | | | | | a mis-named unit test such that so-called "schema" types like :class:`.Boolean` and :class:`.Enum` could no longer be pickled. fixes #3144
* - Fixed bug in :class:`.postgresql.array` object where comparisonMike Bayer2014-07-251-0/+10
| | | | | to a plain Python list would fail to use the correct array constructor. Pull request courtesy Andrew. fixes #3141
* - The MySQL dialect will now disable :meth:`.ConnectionEvents.handle_error`Mike Bayer2014-07-251-0/+12
| | | | | | | | | | events from firing for those statements which it uses internally to detect if a table exists or not. This is achieved using an execution option ``skip_user_error_events`` that disables the handle error event for the scope of that execution. In this way, user code that rewrites exceptions doesn't need to worry about the MySQL dialect or other dialects that occasionally need to catch SQLAlchemy specific exceptions.
* - Added a supported :meth:`.FunctionElement.alias` method to functions,Mike Bayer2014-07-241-0/+12
| | | | | | | | | e.g. the ``func`` construct. Previously, behavior for this method was undefined. The current behavior mimics that of pre-0.9.4, which is that the function is turned into a single-column FROM clause with the given alias name, where the column itself is anonymously named. fixes #3137
* merge 0.9.8 startMike Bayer2014-07-241-6/+7
|
* forwards port 0.9 changelog updateMike Bayer2014-07-221-1/+1
|
* - forwards port 0.8 changelog updateMike Bayer2014-07-221-0/+1
|
* - missing 0.8 change forwards portMike Bayer2014-07-221-0/+9
|
* spellingMike Bayer2014-07-221-1/+1
|
* - ticket inlineMike Bayer2014-07-221-5/+1
|
* - update some SQL server tests, supportMike Bayer2014-07-221-1/+3
| | | | - add support for IDENTITY INSERT setting for INSERT with inline VALUES
* - fix missing release dateMike Bayer2014-07-211-0/+1
|
* - Fixed bug introduced in 0.9.5 by new pg8000 isolation level featureMike Bayer2014-07-211-0/+9
| | | | | where engine-level isolation level parameter would raise an error on connect. fixes #3134
* Fix doc gen on Windows platformpr/120Bog2014-07-211-1/+1
| | | | - replaced hardcoded ":" path separator with OS dependent one.
* - Fixed bug in oracle dialect test suite where in one test,Mike Bayer2014-07-181-0/+9
| | | | | 'username' was assumed to be in the database URL, even though this might not be the case. Fixes #3128
* - forwards-port changelog for ref #3093Mike Bayer2014-07-162-9/+14
|
* - Fixed a regression caused by :ticket:`2976` released in 0.9.4 whereMike Bayer2014-07-151-0/+13
| | | | | | | | | | | | | | | | | the "outer join" propagation along a chain of joined eager loads would incorrectly convert an "inner join" along a sibling join path into an outer join as well, when only descendant paths should be receiving the "outer join" propagation; additionally, fixed related issue where "nested" join propagation would take place inappropriately between two sibling join paths. this is accomplished by re-introducing the removed flag "allow_innerjoin", now inverted and named "chained_from_outerjoin". Propagating this flag allows us to know when we have encountered an outerjoin along a load path, without confusing it for state obtained from a sibling path. fixes #3131 ref #2976
* - Fixed a SQLite join rewriting issue where a subquery that is embeddedMike Bayer2014-07-151-0/+11
| | | | | | | | as a scalar subquery such as within an IN would receive inappropriate substitutions from the enclosing query, if the same table were present inside the subquery as were in the enclosing query such as in a joined inheritance scenario. fixes #3130
* - Fix bug in naming convention feature where using a checkMike Bayer2014-07-141-0/+16
| | | | | | | | | | | | | constraint convention that includes ``constraint_name`` would then force all :class:`.Boolean` and :class:`.Enum` types to require names as well, as these implicitly create a constraint, even if the ultimate target backend were one that does not require generation of the constraint such as Postgresql. The mechanics of naming conventions for these particular constraints has been reorganized such that the naming determination is done at DDL compile time, rather than at constraint/table construction time. fixes #3067
* - Fixed a regression from 0.9.5 caused by :ticket:`3025` where theMike Bayer2014-07-141-0/+10
| | | | | | | query used to determine "default schema" is invalid in SQL Server 2000. For SQL Server 2000 we go back to defaulting to the "schema name" parameter of the dialect, which is configurable but defaults to 'dbo'. fixes #3025
* - Added statement encoding to the "SET IDENTITY_INSERT"Mike Bayer2014-07-141-0/+10
| | | | | | | | | statements which operate when an explicit INSERT is being interjected into an IDENTITY column, to support non-ascii table identifiers on drivers such as pyodbc + unix + py2k that don't support unicode statements. ref #3091 as this fix is also in that issue's patch, but is a different issue.
* - In the SQL Server pyodbc dialect, repaired the implementationMike Bayer2014-07-141-0/+12
| | | | | | | | | for the ``description_encoding`` dialect parameter, which when not explicitly set was preventing cursor.description from being parsed correctly in the case of result sets that contained names in alternate encodings. This parameter shouldn't be needed going forward. fixes #3091
* - Fixed a regression from 0.9.0 due to :ticket:`2736` where theMike Bayer2014-07-141-0/+12
| | | | | | | | | :meth:`.Query.select_from` method no longer set up the "from entity" of the :class:`.Query` object correctly, so that subsequent :meth:`.Query.filter_by` or :meth:`.Query.join` calls would fail to check the appropriate "from" entity when searching for attributes by string name. fixes #3083
* -Fixed bug in common table expressions whereby positional boundMike Bayer2014-07-141-0/+9
| | | | | | parameters could be expressed in the wrong final order when CTEs were nested in certain ways. fixes #3090
* - Fixed bug where multi-valued :class:`.Insert` construct would failMike Bayer2014-07-141-0/+9
| | | | | | to check subsequent values entries beyond the first one given for literal SQL expressions. fixes #3069
* need a 1.0.0 hereMike Bayer2014-07-141-0/+1
|
* - Added a "str()" step to the dialect_kwargs iteration forMike Bayer2014-07-141-0/+10
| | | | | | | Python version < 2.6.5, working around the "no unicode keyword arg" bug as these args are passed along as keyword args within some reflection processes. fixes #3123
* - Fixed bug in :class:`.Enum` and other :class:`.SchemaType`Mike Bayer2014-07-131-0/+10
| | | | | | | subclasses where direct association of the type with a :class:`.MetaData` would lead to a hang when events (like create events) were emitted on the :class:`.MetaData`. fixes #3124
* - The :meth:`.TypeEngine.with_variant` method will now accept aMike Bayer2014-07-101-0/+9
| | | | | | type class as an argument which is internally converted to an instance, using the same convention long established by other constructs such as :class:`.Column`. fixes #3122
* - Changed the default value of "raise_on_warnings" to False forMike Bayer2014-07-091-0/+9
| | | | | | | | MySQLconnector. This was set at True for some reason. The "buffered" flag unfortunately must stay at True as MySQLconnector does not allow a cursor to be closed unless all results are fully fetched. fixes #2515 - lots of MySQL tests seemed to not be hitting all backends, so we should be getting some mysqlconnector failures now
* - add 0.9 changelogMike Bayer2014-07-091-0/+9
|
* - Fixed bug where "python setup.py test" wasn't calling intoMike Bayer2014-07-091-0/+8
| | | | | distutils appropriately, and errors would be emitted at the end of the test suite.
* - The "evaulator" for query.update()/delete() won't work with multi-tableMike Bayer2014-07-081-0/+10
| | | | | | | updates, and needs to be set to `synchronize_session=False` or `synchronize_session='fetch'`; this now raises an exception, with a message to change the synchronize setting. This will be only a warning in 0.9.7. fixes #3117
* - add postgresql_regconfig argument to PG dialect for match() operator,jonathan vanasco2014-07-081-0/+11
| | | | implements PG's to_tsquery('regconfig', 'arg') pattern. fixes #3078
* document JSONBMike Bayer2014-07-071-2/+5
|
* changelogMike Bayer2014-07-071-0/+8
|
* Merge pull request #100 from plaes/typosmike bayer2014-07-061-1/+1
|\ | | | | Typo fixes
| * typo: s/founds/foundPriit Laes2014-06-281-1/+1
| |
* | changelog, fixes #3093Mike Bayer2014-07-061-0/+9
| |
* | - changelogMike Bayer2014-07-061-0/+8
| |
* | - rework the entire approach to #3076. As we need to catch all exceptionsMike Bayer2014-07-043-41/+6
| | | | | | | | | | | | | | | | | | | | | | in all cases unconditionally, the number of use cases that go beyond what dbapi_error() is expecting has gone too far for an 0.9 release. Additionally, the number of things we'd like to track is really a lot more than the five arguments here, and ExecutionContext is really not suitable as totally public API for this. So restore dbapi_error to its old version, deprecate, and build out handle_error instead. This is a lot more extensible and doesn't get in the way of anything compatibility-wise.
* | - Added new attributes :attr:`.ExecutionContext.exception` andMike Bayer2014-07-031-0/+10
| | | | | | | | | | | | | | :attr:`.ExecutionContext.is_disconnect` which are meaningful within the :meth:`.ConnectionEvents.dbapi_error` handler to see both the original DBAPI error as well as whether or not it represents a disconnect.
* | - The mechanics of the :meth:`.ConnectionEvents.dbapi_error` handlerMike Bayer2014-07-032-0/+38
| | | | | | | | | | | | | | have been enhanced such that the function handler is now capable of raising or returning a new exception object, which will replace the exception normally being thrown by SQLAlchemy. fixes #3076
* | - Fixed bug where items that were persisted, deleted, or had aMike Bayer2014-07-011-0/+11
| | | | | | | | | | | | | | primary key change within a savepoint block would not participate in being restored to their former state (not in session, in session, previous PK) after the outer transaction were rolled back. fixes #3108
* | - repair the _enable_single_crit method, it was named the sameMike Bayer2014-06-301-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | as the attribute and probably just replaced itself, so that is now _set_enable_single_crit - as a side effect of the main issue fixed here, correct the case in adjust_for_single_inheritance where the same mapper appears more than once in mapper_adapter_map; run through a set() for uniqueness. - Fixed bug in subquery eager loading in conjunction with :func:`.with_polymorphic`, the targeting of entities and columns in the subquery load has been made more accurate with respect to this type of entity and others. Fixes #3106
* | - add new section Working with Raw DBAPI Connections, fixes #2218.Mike Bayer2014-06-301-0/+65
|/
View Lorry Controller Status