allowing for right nested joins as described at :ref:`feature_joins_09`.
However the SQLite workaround produced many regressions in the 2013-2014
period due to its complexity. In 2016, the dialect was modified so that the
-join rewriting logic would only occur for SQLite verisons prior to 3.7.16 after
+join rewriting logic would only occur for SQLite versions prior to 3.7.16 after
bisection was used to identify where SQLite fixed its support for this
construct, and no further issues were reported against the behavior (even
though some bugs were found internally). It is now anticipated that there
:func:`_expression.text` construct in order to illustrate how textual SQL statements
may be invoked. When working with SQLAlchemy, textual SQL is actually more
of the exception rather than the norm, as the Core expression language
-and the ORM both abstract away the textual representation of SQL. Hpwever, the
+and the ORM both abstract away the textual representation of SQL. However, the
:func:`_expression.text` construct itself also provides some abstraction of textual
SQL in that it normalizes how bound parameters are passed, as well as that
it supports datatyping behavior for parameters and result set rows.
possible that the underlying DBAPI connection may not support shared
access between threads. Check the DBAPI documentation for details.
- The Connection object represents a single dbapi connection checked out
+ The Connection object represents a single DBAPI connection checked out
from the connection pool. In this state, the connection pool has no affect
upon the connection, including its expiration or timeout state. For the
connection pool to properly manage connections, connections should be
return self._execution_options.get("schema_translate_map", None)
def schema_for_object(self, obj):
- """return the schema name for the given schema item taking into
+ """Return the schema name for the given schema item taking into
account current schema translate map.
"""
@property
def lastrowid(self):
- """return the 'lastrowid' accessor on the DBAPI cursor.
+ """Return the 'lastrowid' accessor on the DBAPI cursor.
This is a DBAPI specific method and is only functional
for those backends which support it, for statements
"""Check the existence of a particular index name in the database.
Given a :class:`_engine.Connection` object, a string
- `table_name` and stiring index name, return True if an index of the
+ `table_name` and string index name, return True if an index of the
given name on the given table exists, false otherwise.
The :class:`.DefaultDialect` implements this in terms of the
None and the ending value. Prefer to use iterative / collection
methods which support scalar None values.
- this method is provided for backwards compatibility with
+ This method is provided for backwards compatibility with
SQLAlchemy 1.x.x.
To fetch the first row of a result only, use the
When all rows are exhausted, returns an empty list.
- this method is provided for backwards compatibility with
+ This method is provided for backwards compatibility with
SQLAlchemy 1.x.x.
To fetch rows in groups, use the :meth:`._result.Result.partitions`
This object is suitable to be passed directly to a
:func:`~sqlalchemy.create_engine` call. The fields of the URL are parsed
- from a string by the :func:`.make_url` function. the string
+ from a string by the :func:`.make_url` function. The string
format of the URL is an RFC-1738-style string.
All initialization parameters are available as public attributes.
# This allows an Events subclass to define additional utility
# methods made available to the target via
# "self.dispatch._events.<utilitymethod>"
- # @staticemethod to allow easy "super" calls while in a metaclass
+ # @staticmethod to allow easy "super" calls while in a metaclass
# constructor.
cls.dispatch = dispatch_cls(None)
dispatch_cls._events = cls
projects / thirdparty / sqlalchemy / sqlalchemy.git / commitdiff
