summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* 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
|/
* - Fixed a bug within the custom operator plus :meth:`.TypeEngine.with_variant`Mike Bayer2014-06-271-0/+9
| | | | | | system, whereby using a :class:`.TypeDecorator` in conjunction with variant would fail with an MRO error when a comparison operator was used. fixes #3102
* wrong version numberMike Bayer2014-06-271-1/+1
|
* - MySQL error 2014 "commands out of sync" appears to be raised as aMike Bayer2014-06-271-0/+10
| | | | | | | ProgrammingError, not OperationalError, in modern MySQL-Python versions; all MySQL error codes that are tested for "is disconnect" are now checked within OperationalError and ProgrammingError regardless. fixes #3101
* - Fixed bug involving dynamic attributes, that was again a regressionMike Bayer2014-06-261-0/+8
| | | | | | of :ticket:`3060` from verision 0.9.5. A self-referential relationship with lazy='dynamic' would raise a TypeError within a flush operation. fixes #3099
* add missing release dateMike Bayer2014-06-251-1/+1
|
* - Fixed bug when the declarative ``__abstract__`` flag was not beingMike Bayer2014-06-251-0/+14
| | | | | | | distinguished for when it was actually the value ``False``. The ``__abstract__`` flag needs to acutally evaluate to a True value at the level being tested. fixes #3097
* fix pullreq link in changelog_09.rst edited online with Bitbucketuralbash2014-06-241-3/+2
|
* - reverse course in #3061 so that we instead no longer set None in the attributeMike Bayer2014-06-232-17/+8
| | | | | | | | | when we do a get; we return the None as always but we leave the dict blank and the loader callable still in place. The case for this implicit get on a pending object is not super common and there really should be no change in state at all when this operation proceeds. This change is more dramatic as it reverses a behavior SQLA has had since the first release. fixes #3061
* - Reverted the change for :ticket:`3060` - this is a unit of workMike Bayer2014-06-231-0/+20
| | | | | | | fix that is updated more comprehensively in 1.0 via :ticket:`3061`. The fix in :ticket:`3060` unfortunately produces a new issue whereby an eager load of a many-to-one attribute can produce an event that is interpreted into an attribute change.
* 0.9.5 released dateMike Bayer2014-06-231-0/+1
|
* fix changelogMike Bayer2014-06-231-0/+2
|
* - Additional checks have been added for the case where an inheritingMike Bayer2014-06-202-0/+91
| | | | | | | | | | mapper is implicitly combining one of its column-based attributes with that of the parent, where those columns normally don't necessarily share the same value. This is an extension of an existing check that was added via :ticket:`1892`; however this new check emits only a warning, instead of an exception, to allow for applications that may be relying upon the existing behavior. fixes #3042
* additional version notesMike Bayer2014-06-201-5/+5
|
* add missing version markersMike Bayer2014-06-201-0/+4
|
* - The :paramref:`.Column.nullable` flag is implicitly set to ``False``Mike Bayer2014-06-201-0/+12
| | | | | | | | | when that :class:`.Column` is referred to in an explicit :class:`.PrimaryKeyConstraint` for that table. This behavior now matches that of when the :class:`.Column` itself has the :paramref:`.Column.primary_key` flag set to ``True``, which is intended to be an exactly equivalent case. fixes #3023
* - Added a new type :class:`.postgresql.OID` to the Postgresql dialect.Mike Bayer2014-06-202-1/+13
| | | | | | | | While "oid" is generally a private type within PG that is not exposed in modern versions, there are some PG use cases such as large object support where these types might be exposed, as well as within some user-reported schema reflection use cases. fixes #3002
* - Fixed bug where column names added to ``mysql_length`` parameterMike Bayer2014-06-181-0/+11
| | | | | | | | on an index needed to have the same quoting for quoted names in order to be recognized. The fix makes the quotes optional but also provides the old behavior for backwards compatibility with those using the workaround. fixes #3085
* - Modified the behavior of :func:`.orm.load_only` such that primary keyMike Bayer2014-06-121-0/+12
| | | | | | | | | columns are always added to the list of columns to be "undeferred"; otherwise, the ORM can't load the row's identity. Apparently, one can defer the mapped primary keys and the ORM will fail, that hasn't been changed. But as load_only is essentially saying "defer all but X", it's more critical that PK cols not be part of this deferral. fixes #3080
* - changelogMike Bayer2014-06-081-0/+7
|
* Merged in univerio/sqlalchemy/materialized_paths (pull request #21) Mike Bayer2014-06-081-0/+5
|\ | | | | Materialized paths example
| * Materialized paths example.Jack Zhou2014-06-071-0/+5
| |
* | changelogMike Bayer2014-06-081-0/+8
|/
* - remove drizzle dialectMike Bayer2014-05-304-77/+32
| | | | | - restore mysqldb fully within dialects/mysql/, it's no longer a connector. fixes #2984
* - vastly improve the "safe close cursor" tests in test_reconnectMike Bayer2014-05-301-0/+14
| | | | | | | | | | | - Fixed bug which would occur if a DBAPI exception occurs when the engine first connects and does its initial checks, and the exception is not a disconnect exception, yet the cursor raises an error when we try to close it. In this case the real exception would be quashed as we tried to log the cursor close exception via the connection pool and failed, as we were trying to access the pool's logger in a way that is inappropriate in this very specific scenario. fixes #3063
* - The ``__mapper_args__`` dictionary is copied from a declarativeMike Bayer2014-05-301-0/+13
| | | | | | | | | mixin or abstract class when accessed, so that modifications made to this dictionary by declarative itself won't conflict with that of other mappings. The dictionary is modified regarding the ``version_id_col`` and ``polymorphic_on`` arguments, replacing the column within with the one that is officially mapped to the local class/table. fixes #3062
* fix typoMike Bayer2014-05-301-3/+3
|
* Merged in chrisw/sqlalchemy/more_range_docs (pull request #20) Mike Bayer2014-05-302-1/+31
|\ | | | | | | | | more docs for using psycopg2 range types, specifically instantiating models with them fixes #3046
| * more docs for using psycopg2 range types, specifically instantiating models ↵Chris Withers2014-05-252-1/+31
| | | | | | | | with them
* | - changelog + docs for pg8000 transaction isolation levelMike Bayer2014-05-301-0/+8
| |
* | - The psycopg2 ``.closed`` accessor is now consulted when determiningMike Bayer2014-05-301-0/+13
| | | | | | | | | | | | | | | | | | if an exception is a "disconnect" error; ideally, this should remove the need for any other inspection of the exception message to detect disconnect, however we will leave those existing messages in place as a fallback. This should be able to handle newer cases like "SSL EOF" conditions. Pull request courtesy Dirk Mueller. fixes #3021
* | - Related to :ticket:`3060`, an adjustment has been made to the unitMike Bayer2014-05-301-0/+11
| | | | | | | | | | | | | | | | | | | | of work such that loading for related many-to-one objects is slightly more aggressive, in the case of a graph of self-referential objects that are to be deleted; the load of related objects is to help determine the correct order for deletion if passive_deletes is not set. - revert the changes to test_delete_unloaded_m2o, these deletes do in fact need to occur in the order of the two child objects first.
* | add ticketMike Bayer2014-05-291-0/+2
| |
* | - Adjustment to attribute mechanics concerning when a value isMike Bayer2014-05-293-4/+100
| | | | | | | | | | | | | | | | | | | | | | | | | | | | implicitly initialized to None via first access; this action, which has always resulted in a population of the attribute, now emits an attribute event just like any other attribute set operation and generates the same kind of history as one. Additionally, many mapper internal operations will no longer implicitly generate these "None" values when various never-set attributes are checked. These are subtle behavioral fixes to attribute mechanics which provide a better solution to the problem of :ticket:`3060`, which also involves recognition of attributes explicitly set to ``None`` vs. attributes that were never set. fixes #3061
* | relative hereMike Bayer2014-05-291-0/+1
| |
* | - correct the size on side elementsMike Bayer2014-05-292-25/+60
| |
* | - re-merge doc_nav. We've removed the whole idea of a "fixed top", and ↵Mike Bayer2014-05-295-122/+158
|\ \ | | | | | | | | | | | | | | | | | | | | | moved the "fixed" thing entirely to the left side. The content now regains full vertical real estate, such that there's no workarounds needed for anchors, they work directly again. we had to reorganize the whole layout to accommodate this however.
| * | fixMike Bayer2014-05-291-1/+1
| | |
| * | moreMike Bayer2014-05-291-3/+4
| | |
| * | - all new approach which allows the main text to be on the topMike Bayer2014-05-294-132/+155
| | |
| * | - add some more height here so that anchors come outMike Bayer2014-05-271-2/+2
| | |
View Lorry Controller Status