#29222: Substr on NULL values returns incorrect results with pattern lookups.
-------------------------------------+-------------------------------------
     Reporter:  Mariusz Felisiak     |                    Owner:  Siddharth
                                     |  Panditrao
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:  Oracle               |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):

 Hello Siddhahrt,

 > Should I update the ticket status myself, or will a maintainer handle
 that?

 Mariusz has already taken care of that in comment:8 so you should be all
 set.

 > And would it be helpful if I added a test or docs clarifying this
 Oracle-specific behavior?

 I think we're already covered with
 [https://docs.djangoproject.com/en/6.0/ref/databases/#null-and-empty-
 strings this documentation]. The fact it states

 > When fetching from the database, it is assumed that a `NULL` value in
 one of these fields **really means the empty string**, and the data is
 silently converted to reflect this assumption.

 strengthen my believe we're making the right call here as we consider that
 `NULL` means empty string by continuing to match all rows.

 > This was my first attempt at contributing to Django, so I appreciate you
 taking the time to walk through the reasoning.

 Happy to help and thanks for the triage and giving it a shot.

 Triaging issues and spending time understanding them is often more
 valuable than landing code itself as it strengthen our common
 understanding of the problem and allow us to
 [https://github.com/django/django/pull/19793#discussion_r2637685073 build
 a consistent experience] accross the diverse interfaces the ORM provides.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/29222#comment:10>
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 view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019b4182ca2a-640989e7-9e61-4a48-9609-7d477d72e048-000000%40eu-central-1.amazonses.com.

Reply via email to