Changes between Initial Version and Version 1 of Ticket #34564, comment 19
- Timestamp:
- May 26, 2023, 9:07:05 PM (18 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #34564, comment 19
initial v1 1 1 Django doesn't support TimescaleDB so any change against it is not considered a regression from our perspective. You might have run into bugs with TimescaleDB for all we know. 2 3 > I suppose the old convert_value function was there for those scenarios 4 5 It could have been there solely to support a subset of the cases that `empty_result_set_value` covers for aggregation and selects now. 2 6 3 7 The fact you cannot reproduce against SQLite, Postgres, MySQL, or Oracle might explain why this was not caught by the test suite in the first place which would make more sense given how common such annotations are.