summaryrefslogtreecommitdiff
path: root/doc/build
Commit message (Collapse)AuthorAgeFilesLines
* - Fixed bug in :class:`.AbstractConcreteBase` extension whereMike Bayer2015-07-131-0/+11
| | | | | | | | | a column setup on the ABC base which had a different attribute name vs. column name would not be correctly mapped on the final base class. The failure on 0.9 would be silent whereas on 1.0 it raised an ArgumentError, so may not have been noticed prior to 1.0. fixes #3480
* - try to note under insert.values(), if you needMike Bayer2015-07-081-1/+5
| | | | | | "multiple parameter sets" there is a much more common case which works equally well for INSERT/UPDATE/DELETE e.g. executemany(). reference #3476
* - fix the link here fixes 3473Mike Bayer2015-07-031-1/+1
|
* - Fixed 1.0 regression where value objects that overrideMike Bayer2015-07-011-0/+11
| | | | | | | | | ``__eq__()`` to return a non-boolean-capable object, such as some geoalchemy types as well as numpy types, were being tested for ``bool()`` during a unit of work update operation, where in 0.9 the return value of ``__eq__()`` was tested against "is True" to guard against this. fixes #3469
* - Fixed 1.0 regression where a "deferred" attribute would not populateMike Bayer2015-06-291-0/+12
| | | | | | | | | | correctly if it were loaded within the "optimized inheritance load", which is a special SELECT emitted in the case of joined table inheritance used to populate expired or unloaded attributes against a joined table without loading the base table. This is related to the fact that SQLA 1.0 no longer guesses about loading deferred columns and must be directed explicitly. fixes #3468
* - Fixed 1.0 regression where the "parent entity" of a synonym-Mike Bayer2015-06-271-0/+15
| | | | | | | | | | | | | mapped attribute on top of an :func:`.aliased` object would resolve to the original mapper, not the :func:`.aliased` version of it, thereby causing problems for a :class:`.Query` that relies on this attribute (e.g. it's the only representative attribute given in the constructor) to figure out the correct FROM clause for the query. fixes #3466 - apply consitency to ._parententity vs. __clause_element__()._annotations['parententity'] in terms of aliased class, test it all.
* 1.0.6rel_1_0_6Mike Bayer2015-06-252-2/+3
|
* - Fixed a major regression in the 1.0 series where the version_id_counterMike Bayer2015-06-241-0/+15
| | | | | | | | | | | | | feature would cause an object's version counter to be incremented when there was no net change to the object's row, but instead an object related to it via relationship (e.g. typically many-to-one) were associated or de-associated with it, resulting in an UPDATE statement that updates the object's version counter and nothing else. In the use case where the relatively recent "server side" and/or "programmatic/conditional" version counter feature were used (e.g. setting version_id_generator to False), the bug could cause an UPDATE without a valid SET clause to be emitted. fixes #3465
* - edits to this sectionMike Bayer2015-06-222-16/+20
|
* - add a new FAQ on re-reading of data within a transaction, sinceMike Bayer2015-06-222-3/+71
| | | | this is definitely something that is asked regularly.
* - Fixed issue when using :class:`.VARBINARY` type in conjunction withMike Bayer2015-06-221-0/+11
| | | | | | | | | an INSERT of NULL + pyodbc; pyodbc requires a special object be passed in order to persist NULL. As the :class:`.VARBINARY` type is now usually the default for :class:`.LargeBinary` due to :ticket:`3039`, this issue is partially a regression in 1.0. The pymssql driver appears to be unaffected. fixes #3464
* - Re-fixed this issue first released in 1.0.5 to fix psycopg2cffiMike Bayer2015-06-221-0/+10
| | | | | | | | JSONB support once again, as they suddenly switched on unconditional decoding of JSONB types in version 2.7.1. Version detection now specifies 2.7.1 as where we should expect the DBAPI to do json encoding for us. fixes #3439
* - more edits, references #3461Mike Bayer2015-06-191-16/+25
|
* - for #3455Mike Bayer2015-06-191-0/+17
| | | | | | | | | - changelog - versionadded + reflink for new pg storage parameters doc - pep8ing - add additional tests to definitely check that the Index object is created all the way with the opts we want fixes #3455
* - fix the bulletsMike Bayer2015-06-192-19/+26
| | | | | | - tone down the "never dispose an engine" language - refer to NullPool for the "I don't like pooling" use case references #3461
* - Fixed 1.0 regression where the enhanced behavior of single-inheritanceMike Bayer2015-06-191-0/+10
| | | | | | | | joins of :ticket:`3222` takes place inappropriately for a JOIN along explicit join criteria with a single-inheritance subclass that does not make use of any discriminator, resulting in an additional "AND NULL" clause. fixes #3462
* - add explciit section on engine disposal, fixes #3461Mike Bayer2015-06-191-0/+54
|
* - Repaired the :class:`.ExcludeConstraint` construct to support commonMike Bayer2015-06-161-0/+9
| | | | | | | features that other objects like :class:`.Index` now do, that the column expression may be specified as an arbitrary SQL expression such as :obj:`.cast` or :obj:`.text`. fixes #3454
* - add a subsection on how to use Sequence with server_default,Mike Bayer2015-06-161-0/+40
| | | | fixes #3453
* Merge branch 'pr182'Mike Bayer2015-06-141-0/+11
|\
| * - add test cases for pullreq github:182, where we add a newMike Bayer2015-06-141-0/+11
| | | | | | | | | | | | | | | | "max_row_buffer" execution option for BufferedRowResultProxy - also add documentation, changelog and version notes - rework the max_row_buffer argument to be interpreted from the execution options upfront when the BufferedRowResultProxy is first initialized.
* | - add changelog for #3451, with 09485d733131b667813f44eb0b6807b698668ee7 ↵Mike Bayer2015-06-131-0/+10
|/ | | | | | fixes #3451 - also add a bulk_insert_mappings test
* - Fixed an unexpected-use regression whereby custom :class:`.Comparator`Mike Bayer2015-06-111-0/+13
| | | | | | | | | | objects that made use of the ``__clause_element__()`` method and returned an object that was an ORM-mapped :class:`.InstrumentedAttribute` and not explicitly a :class:`.ColumnElement` would fail to be correctly handled when passed as an expression to :meth:`.Session.query`. The logic in 0.9 happened to succeed on this, so this use case is now supported. fixes #3448
* - add an 0.9 migration note regarding TypeEngine's defaultMike Bayer2015-06-101-1/+65
| | | | constructor removal; fixes #3446
* - Fixed a bug where clause adaption as applied to a :class:`.Label`Mike Bayer2015-06-091-0/+14
| | | | | | | | | | | | object would fail to accommodate the labeled SQL expression in all cases, such that any SQL operation that made use of :meth:`.Label.self_group` would use the original unadapted expression. One effect of this would be that an ORM :func:`.aliased` construct would not fully accommodate attributes mapped by :obj:`.column_property`, such that the un-aliased table could leak out when the property were used in some kinds of SQL comparisons. fixes #3445
* - add a migration note for the query.update()/query.delete() changeMike Bayer2015-06-091-1/+15
| | | | in #3349
* - add a comment, also I think we want to expire before we do theMike Bayer2015-06-091-1/+6
| | | | new begin, as begin_nested() does a flush
* Merge remote-tracking branch 'origin/pr/180' into pr180Mike Bayer2015-06-091-1/+3
|\
| * Expire session in testing transaction handlingpr/180Charles-Axel Dein2015-06-081-1/+3
| |
* | - Fixed an internal "memoization" routine for method types suchMike Bayer2015-06-081-0/+8
| | | | | | | | | | that a Python descriptor is no longer used; repairs inspectability of these methods including support for Sphinx documentation.
* | - start 1.0.6Mike Bayer2015-06-081-0/+3
|/
* - 1.0.5rel_1_0_5Mike Bayer2015-06-072-2/+3
|
* - Added new engine event :meth:`.ConnectionEvents.engine_disposed`.Mike Bayer2015-06-061-0/+6
| | | | Called after the :meth:`.Engine.dispose` method is called.
* - Repaired some typing and test issues related to the pypyMike Bayer2015-06-051-0/+11
| | | | | | | | | psycopg2cffi dialect, in particular that the current 2.7.0 version does not have native support for the JSONB type. The version detection for psycopg2 features has been tuned into a specific sub-version for psycopg2cffi. Additionally, test coverage has been enabled for the full series of psycopg2 features under psycopg2cffi. fixes #3439
* - correctly categorize this changelog entry and rewrite itMike Bayer2015-06-031-15/+10
| | | | | to be understandable, now that there's some time past since I first wrote it
* - changelog for pr bitbucket:54Mike Bayer2015-06-031-0/+10
| | | | - alter the approach so that the initial callable is working just like add_criteria/with_criteria
* Fix typo in directivepr/177Éric Araujo2015-05-291-2/+1
|
* Remove spaces around kwargs in metadata.rstpr/175Jochen Van de Velde2015-05-261-7/+7
|
* - Fixed bug where known boolean values used byMike Bayer2015-05-261-0/+9
| | | | | | | | :func:`.engine_from_config` were not being parsed correctly; these included ``pool_threadlocal`` and the psycopg2 argument ``use_native_unicode``. fixes #3435 - add legacy_schema_aliasing config parsing for mssql - move use_native_unicode config arg to the psycopg2 dialect
* - turn some dials to try to get more log outputMike Bayer2015-05-252-2/+2
|
* - work around RTD issue #1293, take oneMike Bayer2015-05-252-1/+33
|
* - Added a new dialect flag to the MSSQL dialectMike Bayer2015-05-241-0/+28
| | | | | | | | | | | | | | | | | | | | | | | ``legacy_schema_aliasing`` which when set to False will disable a very old and obsolete behavior, that of the compiler's attempt to turn all schema-qualified table names into alias names, to work around old and no longer locatable issues where SQL server could not parse a multi-part identifier name in all circumstances. The behavior prevented more sophisticated statements from working correctly, including those which use hints, as well as CRUD statements that embed correlated SELECT statements. Rather than continue to repair the feature to work with more complex statements, it's better to just disable it as it should no longer be needed for any modern SQL server version. The flag defaults to True for the 1.0.x series, leaving current behavior unchanged for this version series. In the 1.1 series, it will default to False. For the 1.0 series, when not set to either value explicitly, a warning is emitted when a schema-qualified table is first used in a statement, which suggests that the flag be set to False for all modern SQL Server versions. fixes #3424 fixes #3430
* - Adjustments to the engine plugin hook, such that theMike Bayer2015-05-221-0/+11
| | | | | | | | :meth:`.URL.get_dialect` method will continue to return the ultimate :class:`.Dialect` object when a dialect plugin is used, without the need for the caller to be aware of the :meth:`.Dialect.get_dialect_cls` method. reference #3379
* - Fixed regression in the :mod:`sqlalchemy.ext.mutable` extensionMike Bayer2015-05-211-0/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | as a result of the bugfix for :ticket:`3167`, where attribute and validation events are no longer called within the flush process. The mutable extension was relying upon this behavior in the case where a column level Python-side default were responsible for generating the new value on INSERT or UPDATE, or when a value were fetched from the RETURNING clause for "eager defaults" mode. The new value would not be subject to any event when populated and the mutable extension could not establish proper coercion or history listening. A new event :meth:`.InstanceEvents.refresh_flush` is added which the mutable extension now makes use of for this use case. fixes #3427 - Added new event :meth:`.InstanceEvents.refresh_flush`, invoked when an INSERT or UPDATE level default value fetched via RETURNING or Python-side default is invoked within the flush process. This is to provide a hook that is no longer present as a result of :ticket:`3167`, where attribute and validation events are no longer called within the flush process. - Added a new semi-public method to :class:`.MutableBase` :meth:`.MutableBase._get_listen_keys`. Overriding this method is needed in the case where a :class:`.MutableBase` subclass needs events to propagate for attribute keys other than the key to which the mutable type is associated with, when intercepting the :meth:`.InstanceEvents.refresh` or :meth:`.InstanceEvents.refresh_flush` events. The current example of this is composites using :class:`.MutableComposite`.
* Correcting typo in introspectionpr/173Pierre Rochard2015-05-171-1/+1
|
* - Added support for the case of the misbehaving DBAPI that hasMike Bayer2015-05-151-0/+13
| | | | | | | | | | | pep-249 exception names linked to exception classes of an entirely different name, preventing SQLAlchemy's own exception wrapping from wrapping the error appropriately. The SQLAlchemy dialect in use needs to implement a new accessor :attr:`.DefaultDialect.dbapi_exception_translation_map` to support this feature; this is implemented now for the py-postgresql dialect. fixes #3421
* - The "lightweight named tuple" used when a :class:`.Query` returnsMike Bayer2015-05-141-0/+10
| | | | | | | | rows failed to implement ``__slots__`` correctly such that it still had a ``__dict__``. This is resolved, but in the extremely unlikely case someone was assigning values to the returned tuples, that will no longer work. fixes #3420
* - Fixed bug where in the case that a pool checkout event handler is usedMike Bayer2015-05-141-0/+20
| | | | | | | | | | | | | | | | | and the database can no longer be connected towards, that the checkout handler failure is caught, the attempt to re-acquire the connection also raises an exception, but the underlying connection record is not immediately re-checked in before the exception is propagated outwards, having the effect that the checked-out record does not close itself until the stack trace it's associated with is garbage collected, preventing that record from being used for a new checkout until we leave the scope of the stack trace. This can lead to confusion in the specific case of when the number of current stack traces in memory exceeds the number of connections the pool can return, as the pool will instead begin to raise errors about no more checkouts available, rather than attempting a connection again. The fix applies a checkin of the record before re-raising. fixes #3419
* - Added official support for a CTE used by the SELECT presentMike Bayer2015-05-081-0/+14
| | | | | | | | | | | inside of :meth:`.Insert.from_select`. This behavior worked accidentally up until 0.9.9, when it no longer worked due to unrelated changes as part of :ticket:`3248`. Note that this is the rendering of the WITH clause after the INSERT, before the SELECT; the full functionality of CTEs rendered at the top level of INSERT, UPDATE, DELETE is a new feature targeted for a later release. fixes #3418
* - start 1.0.5Mike Bayer2015-05-081-0/+3
|
View Lorry Controller Status