Changes between Initial Version and Version 1 of Ticket #27147, comment 12


Ignore:
Timestamp:
Jun 15, 2021, 8:53:05 PM (3 years ago)
Author:
Guilherme Martins Crocetti

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #27147, comment 12

    initial v1  
    33I'm currently facing a problem related to this ticket: I have a `DateTimeRangeField` field and there's no easy way, other than writing a custom `ModelForm` and subclassing `forms.DateTimeRangeField`, to customize a bound other than the default "[)". These values are represented by `tstzrange`, one of the types that does not "suffer" of the aforementioned canonical representation https://www.postgresql.org/docs/current/rangetypes.html#RANGETYPES-DISCRETE.
    44
    5 Is this issue still relevant for the current state of Django ? IMO it's a good feature to add...
     5Is this issue still relevant for the current state of Django ? IMO it's a good feature to add (I'm available to work on it)...
    66
    77Looking forward for opinions.
Back to Top