-
-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support using auto
with Postgres ArrayField
s
#288
Support using auto
with Postgres ArrayField
s
#288
Conversation
Currently it seems like there's two issues here:
|
Shouldn't we use psycopg3 ? Django by default now uses psycopg3 |
The dependency here is a "dev" one and mostly for tests, meaning that if we used |
Why was this PR was closed and not merged? |
@bellini666 do you think we should get this in? |
Yes I do! It makes sense Not sure why @colinmcdonald22 closed this, but I can take over it to ensure it will get in |
@bellini666 |
I need this! |
You shall have this #567 |
Description
Previously, any
django.contrib.postgres.fields.ArrayField
s used in models had to be typed manually (say, aslist[MyEnum]
). Now they're compatible withauto
, and resolve to aList
of the type ofbase_field
.Types of Changes
Issues Fixed or Closed by This PR
Fix #200
Checklist