Opened 8 weeks ago

Last modified 5 days ago

#28643 assigned New feature

Complete the ORM Function Library

Reported by: Matthew Pava Owned by: JunyiJ
Component: Database layer (models, ORM) Version: master
Severity: Normal Keywords:
Cc: josh.smeaton@…, felixxm, Shai Berger Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by felixxm)

I was surprised to learn that we didn't have a StrIndex function until version 2, and yet we had Substr since at least version 1.8. I wonder how users were using Substr without also finding a use for StrIndex this whole time. Anyway, since we seem to be adding these functions one at a time, why don't we work on trying to get the built-ins implemented in one sweep instead?

We may even want to split the documentation page (https://docs.djangoproject.com/en/dev/ref/models/database-functions/) into further categories with String functions and Numeric functions.

This is just a sample checklist. There are probably several more that I have missed. These functions are available directly out of the box with PostgreSQL.

String functions not yet implemented:
ASCII(): Returns numeric value of left-most character
CHR(): Character with the given code.
LEFT(): Returns the leftmost number of characters as specified
LPAD(): Returns the string argument, left-padded with the specified string
MD5(): Calculates the MD5 hash of string, returning the result in hexadecimal
REPEAT(): Repeats a string the specified number of times
REPLACE(): Replaces occurrences of a specified string
REVERSE(): Reverse the characters in a string
RIGHT(): Returns the specified rightmost number of characters
RPAD(): Appends string the specified number of times
LTRIM(): Removes leading spaces (PR #9220)
RTRIM(): Removes trailing spaces (PR #9220)
TRIM(): Removes leading and trailing spaces (PR #9220)

Numeric functions:
ABS(): Returns the absolute value.
ACOS(): Returns the arccosine.
ASIN(): Returns the arcsine.
ATAN(): Returns the arctangent.
ATAN2(): Returns the arctangent of the two variables passed to it.
CEILING(): Returns the smallest integer value that is not less than a numeric expression
COS(): Returns the cosine expressed in radians.
COT(): Returns the cotangent.
DEGREES(): Returns a numeric expression converted from radians to degrees.
EXP(): Returns the base of the natural logarithm (e) raised to the power of a numeric expression.
FLOOR(): Returns the largest integer value that is not greater than a numeric expression.
LOG(): Returns the natural logarithm of a numeric expression.
MOD(): Returns the remainder of one expression by diving by another expression.
PI(): Returns the value of pi
POWER(): Returns the value of one expression raised to the power of another expression
RADIANS(): Returns the value of an expression converted from degrees to radians.
ROUND(): Returns a numeric expression rounded to an integer. Can be used to round an expression to a number of decimal points
SIN(): Returns the sine given in radians.
SQRT(): Returns the square root.
TAN(): Returns the tangent expressed in radians.

Change History (20)

comment:1 Changed 8 weeks ago by Josh Smeaton

I had hoped that the 3rd party community would take care of providing "Function Packs" for each of the backends. But functions are fairly easy to create in your own project if you need them so I guess few people have bothered to group them into a distributable package.

I would prefer that the django ecosystem had a standard group of function expressions that can be used across backends, rather than a bunch of similar but not quite the same implementations. Then 3rd party libraries can depend on the known good versions and everyone is better off. Since the community hasn't seemed to provide such a library (that I'm aware of), I think it's fine for Django to do so.

Splitting the module up into string/numeric/date types sounds fine. Let's take inspiration from postgres and other db vendor docs so navigating them is familiar. Let's begin with functions that have standard support across our 4 backends, then look into what's left over. If we can approximate support by combining other functions we can do that. Otherwise if a particular function only has support for one or two backends we can consider ignoring it or implementing in a contrib module.

comment:2 Changed 8 weeks ago by Josh Smeaton

Cc: josh.smeaton@… added
Triage Stage: UnreviewedAccepted

comment:3 Changed 7 weeks ago by felixxm

Cc: felixxm added

comment:4 Changed 7 weeks ago by JunyiJ

Owner: changed from nobody to JunyiJ
Status: newassigned

comment:5 Changed 7 weeks ago by Josh Smeaton

For whoever wants to begin here, I think a good plan of attack will be a PR per function or per a small set of functions. Then the commit message would be something like "Refs #28643 -- Added X, Y, Z functions".

That way we can get through smaller pieces at a time, without such a large burden being placed on any one individual. We could also get some newer contributors to help in this way. Each function on its own should be a relatively easy thing to implement. A higher level task of re-organising the layout into functions/string functions/number may be helpful to get the ticket rolling.

comment:6 Changed 7 weeks ago by Matthew Pava

I did find this third-party utility that handles specific PostgreSQL functions. I wonder if there are other backends that they could be ported to.
https://github.com/hypertrack/django-pg-utils

And I also wonder how all of this connects with specific PostgreSQL aggregate functions already builtin to Django:
https://docs.djangoproject.com/en/1.11/ref/contrib/postgres/aggregates/

comment:7 in reply to:  6 Changed 6 weeks ago by Mads Jensen

Replying to Matthew Pava:

I did find this third-party utility that handles specific PostgreSQL functions. I wonder if there are other backends that they could be ported to.
https://github.com/hypertrack/django-pg-utils

From a quick look, these things are already supported by Django.

comment:8 Changed 6 weeks ago by felixxm

Description: modified (diff)

comment:9 Changed 6 weeks ago by felixxm

I prepared patch to reorganize database functions docs and code (PR). I think we should organize code and doc as follows (bolded functions doesn't exist):

  • docs/ref/models/database-functions.txt section Comparison and conversion functions (django/db/models/functions/comparison.py):
    • Cast, Coalesce, Greatest, Least;
  • docs/ref/models/database-functions.txt section Date Functions (django/db/models/functions/datetime.py):
    • Extract, ExtractDay, ExtractHour, ExtractMinute, ExtractMonth, ExtractQuarter, ExtractSecond, ExtractWeek, ExtractWeekDay, ExtractYear, Now, Trunc, TruncDate, TruncDay, TruncHour, TruncMinute, TruncMonth, TruncQuarter, TruncSecond, TruncTime, TruncYear;';
  • docs/ref/models/database-functions.txt section Math Functions (django/db/models/functions/math.py):
    • Abs, Acos, Asin, Atan, Atan2, Ceil, Cos, Cot, Exp, Floor, Log, Mod, Power, Round, Sin, Sqrt, Tan;
  • docs/ref/models/database-functions.txt section Text Functions (django/db/models/functions/text.py):
    • Ascii, Chr, Concat, ConcatPair, Length, Lpad, Lower, Ltrim, Replace, Rpad, Rtrim, StrIndex, Substr, Trim, Upper;
  • docs/ref/models/database-functions.txt section Window Functions (django/db/models/functions/window.py):
    • CumeDist, DenseRank, FirstValue, Lag, LastValue, Lead, NthValue, Ntile, PercentRank, Rank, RowNumber.

Headers and functions in docs and code should be organized alphabetically. Thanks Tim Graham for suggestions.

I'm not convince that following functions should be implemented because there not supported on all databases:

  • LEFT(), MD5(), REPEAT(), REVERSE(), RIGHT(), DEGREES(), PI(), RADIANS().
Last edited 5 weeks ago by felixxm (previous) (diff)

comment:10 Changed 5 weeks ago by Tim Graham

The "Miscellaneous" group is sort of bothering me.

Cast, Coalesce, Greatest, Least sound like candidates for a section called something like "Comparison and conversion functions"

Ascii and Chr sound like they could be "text" related.

Now sounds like a candidate for "Date Functions".

comment:11 Changed 5 weeks ago by felixxm

Agreed. I updated above comment and both PRs.

comment:12 Changed 5 weeks ago by Matthew Pava

In regards to Left() and Right(), they are available in PostgreSQL and MySQL, but not in SQLite or Oracle. However, you can emulate their functionality using the corresponding Substr function in the database backend. I would hate to see us leave those out for that reason alone. At the same time, developers could use the Substr across all databases instead of using Left and Right.

I was also wondering about the use of Trim. Python doesn't use that term; instead, it uses strip. I wonder if that really matters. Some developers may look for a strip functionality in Django ORM not realizing that the databases use the term Trim. Perhaps that could be clarified in the documentation.

comment:13 in reply to:  12 Changed 5 weeks ago by Shai Berger

Cc: Shai Berger added

Replying to Matthew Pava:

I was also wondering about the use of Trim. Python doesn't use that term; instead, it uses strip. I wonder if that really matters. Some developers may look for a strip functionality in Django ORM not realizing that the databases use the term Trim. Perhaps that could be clarified in the documentation.

Unless there is some other use for the term strip in the databases, I'd consider "documenting" this by giving an alias:

class Trim(Transform):
    # ...

Strip = Trim  # Give Trim a more Pythonic name

comment:14 Changed 5 weeks ago by GitHub <noreply@…>

In ad8036d7:

Refs #28643 -- Reorganized database functions docs.

Thanks Tim Graham for the review.

comment:15 Changed 5 weeks ago by Mariusz Felisiak <felisiak.mariusz@…>

In 8b42a18b:

[2.0.x] Refs #28643 -- Reorganized database functions docs.

Thanks Tim Graham for the review.

Backport of ad8036d715d4447b95d485332511b4edb1a40c0e from master

comment:16 Changed 5 weeks ago by GitHub <noreply@…>

In 4f27e475:

Refs #28643 -- Reorganized database functions.

Thanks Tim Graham for the review.

comment:17 Changed 5 weeks ago by felixxm

PR - Ltrim, Rtrim, and Trim with aliases Lstrip, Rstrip, and Strip, respectively.

Last edited 4 weeks ago by felixxm (previous) (diff)

comment:18 Changed 5 weeks ago by Matthew Pava

And, of course, there is a Python lstrip and rstrip as well.

Lstrip = Ltrim  # Give Ltrim a more Pythonic name
Rstrip = Rtrim  # Give Rtrim a more Pythonic name

comment:19 in reply to:  18 Changed 4 weeks ago by felixxm

Replying to Matthew Pava:

And, of course, there is a Python lstrip and rstrip as well.

Lstrip = Ltrim  # Give Ltrim a more Pythonic name
Rstrip = Rtrim  # Give Rtrim a more Pythonic name

I added these aliases.

comment:20 Changed 5 days ago by felixxm

Has patch: set
Note: See TracTickets for help on using tickets.
Back to Top