mirror of
https://github.com/django/django.git
synced 2025-08-11 14:28:54 +00:00
[1.9.x] Normalized "an SQL" spelling.
Backport of 575a9a791e
from master
This commit is contained in:
parent
3c6b9f0bbd
commit
fef3f50e31
8 changed files with 11 additions and 11 deletions
|
@ -71,7 +71,7 @@ We then need to define the ``as_sql`` method. This takes a ``SQLCompiler``
|
|||
object, called ``compiler``, and the active database connection.
|
||||
``SQLCompiler`` objects are not documented, but the only thing we need to know
|
||||
about them is that they have a ``compile()`` method which returns a tuple
|
||||
containing a SQL string, and the parameters to be interpolated into that
|
||||
containing an SQL string, and the parameters to be interpolated into that
|
||||
string. In most cases, you don't need to use it directly and can pass it on to
|
||||
``process_lhs()`` and ``process_rhs()``.
|
||||
|
||||
|
@ -92,7 +92,7 @@ example, ``process_lhs`` returns ``('"author"."name"', [])`` and
|
|||
parameters for the left hand side, but this would depend on the object we have,
|
||||
so we still need to include them in the parameters we return.
|
||||
|
||||
Finally we combine the parts into a SQL expression with ``<>``, and supply all
|
||||
Finally we combine the parts into an SQL expression with ``<>``, and supply all
|
||||
the parameters for the query. We then return a tuple containing the generated
|
||||
SQL string and the parameters.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue