#24194: Oracle Backend Operations
-------------------------------------+-------------------------------------
     Reporter:  kl4us                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  1.7
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by shaib):

 Actually, this ticket appears to require substantial corrections to its
 summary and description.

 First of all, `connection.ops.datetime_trunc_sql` is internal,
 undocumented API. For this, my initial reaction was to want to close this
 ticket as invalid.

 However, there is a real issue here -- `connection.ops.date_trunc_sql` and
 `connection.ops.datetime_trunc_sql` behave differently: The former returns
 just sql, and the latter sql and params. This is a wart and should be
 fixed, even though it is internal API. Also, I haven't reviewed other
 methods -- I'm not sure about the extent of the required clean-up.

 However, the problem is general, and not Oracle-specific. The Oracle-
 specific parts of the description -- including even the name of the field
 (fields with keyword names are known to be problematic on Oracle) -- are
 red herrings.

 Since correcting this ticket according to my understanding would involve a
 complete rewrite, I'm just leaving this comment here for now, waiting for
 approval or rebuttal from the original poster or others.

--
Ticket URL: <https://code.djangoproject.com/ticket/24194#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.022b0e58a9b16a12012fc489f537a2de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to