mirror of
https://github.com/sqlalchemy/sqlalchemy.git
synced 2026-05-28 03:26:01 -04:00
some spelling fixes
This commit is contained in:
Vendored
+1
-1
@@ -1631,7 +1631,7 @@
|
||||
with pytest.
|
||||
|
||||
The test plugin system has also been enhanced to support running
|
||||
tests against mutiple database URLs at once, by specifying the ``--db``
|
||||
tests against multiple database URLs at once, by specifying the ``--db``
|
||||
and/or ``--dburi`` flags multiple times. This does not run the entire test
|
||||
suite for each database, but instead allows test cases that are specific
|
||||
to certain backends make use of that backend as the test is run.
|
||||
|
||||
@@ -269,8 +269,8 @@ class ValuesBase(UpdateBase):
|
||||
It is essential to note that **passing multiple values is
|
||||
NOT the same as using traditional executemany() form**. The above
|
||||
syntax is a **special** syntax not typically used. To emit an
|
||||
INSERT statement against mutliple rows, the normal method is
|
||||
to pass a mutiple values list to the :meth:`.Connection.execute`
|
||||
INSERT statement against multiple rows, the normal method is
|
||||
to pass a multiple values list to the :meth:`.Connection.execute`
|
||||
method, which is supported by all database backends and is generally
|
||||
more efficient for a very large number of parameters.
|
||||
|
||||
@@ -403,7 +403,7 @@ class ValuesBase(UpdateBase):
|
||||
SELECT, multi-valued VALUES clause),
|
||||
:meth:`.ValuesBase.return_defaults` is intended only for an
|
||||
"ORM-style" single-row INSERT/UPDATE statement. The row returned
|
||||
by the statement is also consumed implcitly when
|
||||
by the statement is also consumed implicitly when
|
||||
:meth:`.ValuesBase.return_defaults` is used. By contrast,
|
||||
:meth:`.UpdateBase.returning` leaves the RETURNING result-set
|
||||
intact with a collection of any number of rows.
|
||||
|
||||
Reference in New Issue
Block a user