Hello,
fishing for some ideas here. consider this scenario:
```
...
Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /c/add/
...
Internal Server Error: /c/add/
UnboundLocalError at /c/add/
local variable 'model' referenced before assignment
...
Traceback (most recent call last):
..
Hi Jörg!
>At this point I think ArrayField should always use ARRAY constructor to
benefit from the additional sanity checks. But as noted earlier, ARRAY
also exposes this weird behavior:
Definitely, FYI Daniele Varrazzo from psycopg2 said
https://github.com/psycopg/psycopg2/issues/1507
that
>ARRAY
Week ending October 9, 2022
*Triaged: *
https://code.djangoproject.com/ticket/34070 - Add support for
microseconds to Now() on MySQL and SQLite. (created)
https://code.djangoproject.com/ticket/34071 - Unclear validator messages
for Range(Min/Max)ValueValidator compared to docs. (accepted)
https
@Ion
Well I am not deep enough into django's ArrayField for postgres to tell,
which one is the desired output or right behavioral pattern. For my COPY
FROM rewrite I simply tested several edge cases and tried to get as
close as possible to ArrayField.
From postgres side of things the followi
