Changes between Initial Version and Version 1 of Ticket #34080, comment 9
- Timestamp:
- Oct 13, 2022, 6:11:16 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #34080, comment 9
initial v1 1 1 ok so just my 2¢ worth in investigating this: 2 2 3 Mix-n-matching `array[]` constructor with array literals `{}` seems to be the issue which I reckon has to do with postgres not understanding how to infer the appropriate types when nested and `NULL`s are present. In my experience postgres generally won't do this for complex types including json; see my related ticket #33905. The solution often involves just being more explicit.3 Mix-n-matching `array[]` constructor with array literals `{}` seems to be the issue which I reckon has to do with postgres not understanding how to infer the appropriate types when nested (edit the following is inaccurate) and `NULL`s are present. In my experience postgres generally won't do this for complex types including json; see my related ticket #33905. The solution often involves just being more explicit. 4 4 5 5 I tried manually altering the SQL Django has output for a sample model with nested ArrayField with the following problematic output: