Opened 8 years ago
Closed 8 years ago
#28365 closed Cleanup/optimization (fixed)
Unify date_interval_sql() method with other backend date/datetime/time operations.
| Reported by: | Mariusz Felisiak | Owned by: | Mariusz Felisiak |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
This is a follow up of the discussion in 24194#comment:6 (see also#27802). date_interval_sql behaves differently than others date/datetime/time operations. It returns sql and params whereas the others return just sql.
Change History (3)
comment:1 by , 8 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 8 years ago
| Has patch: | set |
|---|---|
| Summary: | Unify date_interval_sql() method with others backend date/datetime/time operations. → Unify date_interval_sql() method with other backend date/datetime/time operations. |
| Triage Stage: | Accepted → Ready for checkin |
Note:
See TracTickets
for help on using tickets.
PR