Django by default, provides a wide range of field types and generic lookups for queries. This in many cases is more than enough. But there are cases where you need to use types defined for yourself and search operators that are not defined in django lookups and another important case is to make searches requiring the execution of some function in WHERE clause.
In django, for these last two cases, it requires writing SQL statements. djorm-ext-expressions introduces the method manager.where() and some class’es (SqlExpression, SqlFunction, AND, OR, …) to facilite sql construction for advanced cases.
Simple usage
Imagine some django model with postgresql integer array field. You need to find objects in the field containing a set of group numbers.
NOTE: array field is part of django orm extensions package and is located on djorm-ext-pgarray submodule.
Example model definition
from django.db import models
from djorm_expressions.models import ExpressionManager
from .somefiels import ArrayField
class Register(models.Model):
name = models.CharField(max_length=200)
points = ArrayField(dbtype="int")
objects = ExpressionManager()
With this model definition, we can do this searches:
from djorm_expressions.base import SqlExpression, AND, OR
# search all register items that points field contains [2,3]
qs = Register.manager.where(
SqlExpression("points", "@>", [2,3])
)
# search all register items that points fields contains [2,3] or [5,6]
expression = OR(
SqlExpression("points", "@>", [2,3]),
SqlExpression("points", "@>", [5,6]),
)
qs = Register.objects.where(expression)
Also, we can use functions to construct a expression:
from djorm_expressions.base import SqlFunction
class BitLength(SqlFunction):
sql_function = "bit_length"
# search all registers items that bit_length(name) > 20.
qs = Register.objects.where(
SqlExpression(BitLength("name"), ">", 20)
)
I finally can redefine the behavior “SqlExpression” and make it more “object oriented”:
class ArrayExpression(object):
def __init__(self, field):
self.field = field
def contains(self, value):
return SqlExpression(self.field, "@>", value)
def overlap(self, value):
return SqlExpression(self.field, "&&", value)
# search all register items that points field contains [2,3]
qs = Register.objects.where(
ArrayExpression("points").contains([2,3])
)
Metadata
Release files for djorm-ext-expressions 0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| djorm-ext-expressions-0.6.tar.gz | 5.8 kB | Without provenance | Details |
Release files / djorm-ext-expressions-0.6.tar.gz
| Download URL | djorm-ext-expressions-0.6.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0d9e4d297b5f7d9bd5c63d6f9b636f8ebd913a5254c12fcdf64239cb358f7ae
|
|
BLAKE2b-256 checksum How to use checksums |
ca56e5800128bf9dae3336a48db16e3880a41a1c006d837db4a63106136ab950
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for djorm-ext-expressions 0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.