#34962: Support for overriding result of model field values
-------------------------------------+-------------------------------------
     Reporter:  piraka9011           |                    Owner:  nobody
         Type:  New feature          |                   Status:  closed
    Component:  Database layer       |                  Version:  4.2
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:  QuerySet.extra       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Natalia Bidart):

 Hello!

 (EDIT: I was writing this message when David submitted theirs, so while
 David's answer is more accurate, I'll post mine to share the links and doc
 pointers).

 This report seems like a mix of a new feature request and a support
 request. The best place to get answers to your final question ("Is there a
 way to do this w/o using `extra()`?") is using any of the user support
 channels from [https://docs.djangoproject.com/en/dev/faq/help/#how-
 do-i-do-x-why-doesn-t-y-work-where-can-i-go-to-get-help this link]. For
 feature requests, the current procedure is to start a new conversation on
 the [https://forum.djangoproject.com/c/internals/5 Django Forum] to
 present the idea and get community consensus, as per
 [https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
 features/#requesting-features the documented guidelines for requesting
 features].

 Since the goal of this issue tracker is to track issues about Django
 itself, I'll be closing this ticket as invalid following the
 [https://docs.djangoproject.com/en/4.2/internals/contributing/triaging-
 tickets/#closing-tickets Ticket Triaging policy].

 Having said that, what I personally would do is to have different field
 names for the `DateTimeField` and its "processed" milliseconds since
 epoch, and I would have the latter be a `GeneratedField` (or an
 annotation) of the former.

 Thank you!

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34962#comment:2>
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 on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018bb476694e-0bf01762-a587-407e-a9b4-9f23877d723c-000000%40eu-central-1.amazonses.com.

Reply via email to