Changes between Version 12 and Version 14 of Ticket #19884


Ignore:
Timestamp:
Jul 13, 2022, 2:08:21 PM (22 months ago)
Author:
Mariusz Felisiak
Comment:

Both DateTimeField and TimeField use exactly the same datatype i.e. TIMESTAMP, they cannot be distinguished in introspection. IMO, we can treat this ticket as fixed.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #19884

    • Property Resolution → fixed
    • Property Status new → closed

  • Ticket #19884 – Description

    v12 v14  
    22  - ~~CharField lengths not correctly inspected (returns double the length of generated field)~~
    33  - ~~FloatField not correctly inspected (returns DecimalField with max_digits=-127)~~
    4   - DateTimeField is inspected as TimeField
     4  - DateTimeField is inspected as TimeField (**cannot be distinguished**)
    55
    66Getting all these to work correctly will be somewhat hard. So, the suggested short-term fix is to just mark the test as expectedFailure on Oracle. Inspectdb isn't high-priority as the output should be hand-edited in any case.
Back to Top