.. change::
:tags: bug, schema
:tickets: 5919
+ :versions: 1.4.0
Repaired / implemented support for primary key constraint naming
conventions that use column names/keys/etc as part of the convention. In
.. change::
:tags: bug, engine
:tickets: 5929
+ :versions: 1.4.0
Fixed bug where the "schema_translate_map" feature failed to be taken into
account for the use case of direct execution of
.. change::
:tags: bug, orm
:tickets: 5952
+ :versions: 1.4.0
Fixed issue where the process of joining two tables could fail if one of
the tables had an unrelated, unresolvable foreign key constraint which
would raise :class:`_exc.NoReferenceError` within the join process, which
nonetheless could be bypassed to allow the join to complete. The logic
- which tested the exception for signficance within the process would make
+ which tested the exception for significance within the process would make
assumptions about the construct which would fail.
.. change::
:tags: bug, orm
:tickets: 5983
+ :versions: 1.4.0
Removed very old warning that states that passive_deletes is not intended
for many-to-one relationships. While it is likely that in many cases
.. change::
- :tags: bug, orm, postgresql
+ :tags: bug, postgresql
:tickets: 5989
+ :versions: 1.4.0
- Fixed issue where using :class:`_ext.aggregate_order_by` would return
- ARRAY(NullType) under certain conditions.
+ Fixed issue where using :class:`_postgresql.aggregate_order_by` would
+ return ARRAY(NullType) under certain conditions, interfering with
+ the ability of the result object to return data correctly.
.. change::
:tags: bug, orm
:tickets: 6001
+ :versions: 1.4.0
Fixed issue where the :class:`_mutable.MutableComposite` construct could be
placed into an invalid state when the parent object was already loaded, and
.. change::
:tags: bug, sql, sqlite
:tickets: 6007
+ :versions: 1.4.0
Fixed issue where the CHECK constraint generated by :class:`_types.Boolean`
or :class:`_types.Enum` would fail to render the naming convention
:tickets: 5953
Deprecated all schema-level ``.copy()`` methods and renamed to
- ``_copy()``.
+ ``_copy()``. These are not standard Python "copy()" methods as they
+ typically rely upon being instantiated within particular contexts
+ which are passed to the method as optional keyword arguments. The
+ :meth:`_schema.Table.tometadata` method is the public API that provides
+ copying for :class:`_schema.Table` objects.
Fixed bug where the "percent escaping" feature that occurs with dialects
that use the "format" or "pyformat" bound parameter styles was not enabled
- for the :meth:`.Operations.op` and :meth:`.Operations.custom_op` methods,
+ for the :meth:`_sql.Operators.op` and :class:`_sql.custom_op` constructs,
for custom operators that use percent signs. The percent sign will now be
automatically doubled based on the paramstyle as necessary.
Altered the compilation for the :class:`.CTE` construct so that a string is
returned representing the inner SELECT statement if the :class:`.CTE` is
stringified directly, outside of the context of an enclosing SELECT; This
- is the same behavior of :meth:`_FromClause.alias` and
- :meth:`_SelectStatement.subquery`. Previously, a blank string would be
+ is the same behavior of :meth:`_sql.FromClause.alias` and
+ :meth:`_sql.Select.subquery`. Previously, a blank string would be
returned as the CTE is normally placed above a SELECT after that SELECT has
been generated, which is generally misleading when debugging.
class Connection(Connectable):
"""Provides high-level functionality for a wrapped DB-API connection.
- Provides execution support for string-based SQL statements as well as
- :class:`_expression.ClauseElement`, :class:`.Compiled` and
- :class:`.DefaultGenerator`
- objects. Provides a :meth:`begin` method to return :class:`.Transaction`
- objects.
+ **This is the SQLAlchemy 1.x.x version** of the :class:`_engine.Connection`
+ class. For the :term:`2.0 style` version, which features some API
+ differences, see :class:`_future.Connection`.
+
+ The :class:`_engine.Connection` object is procured by calling
+ the :meth:`_engine.Engine.connect` method of the :class:`_engine.Engine`
+ object, and provides services for execution of SQL statements as well
+ as transaction control.
The Connection object is **not** thread-safe. While a Connection can be
shared among threads using properly synchronized access, it is still
:class:`~sqlalchemy.engine.interfaces.Dialect` together to provide a
source of database connectivity and behavior.
+ This is the **SQLAlchemy 1.x version** of :class:`_engine.Engine`. For
+ the :term:`2.0 style` version, which includes some API differences,
+ see :class:`_future.Engine`.
+
An :class:`_engine.Engine` object is instantiated publicly using the
:func:`~sqlalchemy.create_engine` function.
class Connection(_LegacyConnection):
"""Provides high-level functionality for a wrapped DB-API connection.
+ The :class:`_future.Connection` object is procured by calling
+ the :meth:`_future.Engine.connect` method of the :class:`_future.Engine`
+ object, and provides services for execution of SQL statements as well
+ as transaction control.
+
**This is the SQLAlchemy 2.0 version** of the :class:`_engine.Connection`
class. The API and behavior of this object is largely the same, with the
following differences in behavior:
- * The result object returned for results is the :class:`_engine.Result`
- object. This object has a slightly different API and behavior than the
- prior :class:`_engine.CursorResult` object.
+ * The result object returned for results is the
+ :class:`_engine.CursorResult`
+ object, which is a subclass of the :class:`_engine.Result`.
+ This object has a slightly different API and behavior than the
+ :class:`_engine.LegacyCursorResult` returned for 1.x style usage.
* The object has :meth:`_future.Connection.commit` and
:meth:`_future.Connection.rollback` methods which commit or roll back
any special instructions for the SAVEPOINT (this will typically have the
effect that one desires).
- * There are no "nested" connections or transactions.
+ * The :class:`_future.Connection` object does not support "branching",
+ which was a pattern by which a sub "connection" would be used that
+ refers to this connection as a parent.
projects / thirdparty / sqlalchemy / sqlalchemy.git / commitdiff
