diff options
Diffstat (limited to 'docs/ref/models')
| -rw-r--r-- | docs/ref/models/expressions.txt | 2 | ||||
| -rw-r--r-- | docs/ref/models/lookups.txt | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt index a9231e8890..f5140f5df5 100644 --- a/docs/ref/models/expressions.txt +++ b/docs/ref/models/expressions.txt @@ -713,7 +713,7 @@ calling the appropriate methods on the wrapped expression. clone.expression = self.expression.relabeled_clone(change_map) return clone - .. method:: convert_value(self, value, expression, connection, context) + .. method:: convert_value(value, expression, connection, context) A hook allowing the expression to coerce ``value`` into a more appropriate type. diff --git a/docs/ref/models/lookups.txt b/docs/ref/models/lookups.txt index efa38d9a41..bd9831e23d 100644 --- a/docs/ref/models/lookups.txt +++ b/docs/ref/models/lookups.txt @@ -79,7 +79,7 @@ field references, aggregates, and ``Transform`` are examples that follow this API. A class is said to follow the query expression API when it implements the following methods: -.. method:: as_sql(self, compiler, connection) +.. method:: as_sql(compiler, connection) Responsible for producing the query string and parameters for the expression. The ``compiler`` is an ``SQLCompiler`` object, which has a ``compile()`` @@ -95,7 +95,7 @@ following methods: override the generation of the SQL string. See :meth:`Func.as_sql` for example usage. -.. method:: as_vendorname(self, compiler, connection) +.. method:: as_vendorname(compiler, connection) Works like ``as_sql()`` method. When an expression is compiled by ``compiler.compile()``, Django will first try to call ``as_vendorname()``, |