db.models.Func.as_sql()
  • References/Python/Django/API/Models/Query Expressions

as_sql(compiler, connection, function=None, template=None, arg_joiner=None, **extra_context) [source]

2025-01-10 15:47:30
db.models.Expression
  • References/Python/Django/API/Models/Query Expressions

class Expression [source] contains_aggregate

2025-01-10 15:47:30
db.models.query.QuerySet.values_list()
  • References/Python/Django/API/Models/QuerySet API reference

values_list(*fields, flat=False) This is similar to values() except that instead of returning dictionaries, it

2025-01-10 15:47:30
db.models.expressions.RawSQL
  • References/Python/Django/API/Models/Query Expressions

class RawSQL(sql, params, output_field=None) [source] Sometimes database expressions can’t

2025-01-10 15:47:30
db.models.CommaSeparatedIntegerField
  • References/Python/Django/API/Models/Model field reference

class CommaSeparatedIntegerField(max_length=None, **options) [source]

2025-01-10 15:47:30
db.models.DO_NOTHING
  • References/Python/Django/API/Models/Model field reference

DO_NOTHING [source] Take no action. If your database backend enforces referential integrity

2025-01-10 15:47:30
db.models.Field.to_python()
  • References/Python/Django/API/Models/Model field reference

to_python(value) [source] Converts the value into the correct Python object. It acts as the

2025-01-10 15:47:30
db.models.Field.deconstruct()
  • References/Python/Django/API/Models/Model field reference

deconstruct() [source] Returns a 4-tuple with enough information to recreate the field:

2025-01-10 15:47:30
db.models.query.QuerySet.update()
  • References/Python/Django/API/Models/QuerySet API reference

update(**kwargs) Performs an SQL update query for the specified fields, and returns the number of rows matched (which may not

2025-01-10 15:47:30
db.models.functions.datetime.ExtractHour
  • References/Python/Django/API/Models/Database Functions

class ExtractHour(expression, tzinfo=None, **extra) [source] lookup_name

2025-01-10 15:47:30