-
-
Notifications
You must be signed in to change notification settings - Fork 13
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 for the array type #116
Comments
Thanks for submitting the proposal, I do think it is a good idea. The only note is that this would touch a lot of areas in the code base. At a high level:
There are also still some open questions around which sub types are supported within the array. I'm happy for you to work on a pr, just be mindful that this is going to require familiarity with the code base and would require quite a number of test cases to be written. It would also require some thinking around integration tests as they are currently run against SQLite. The options are (1) introducing a test dependency for Postgres, (2) using some sort of docker image or (3) reserving this for the Azure based integration tests. I'm leaning towards (3) with a potential for (2) but I'm not sure if the added complexity is worth it. |
thanks for the reply and all the details! super helpful. I think i will hold off for now on the pr then and instead spend some time to get more familiar with the code base, especially on the tests. |
Hi @anovis. I was wondering if you had any updates on the status of this PR. I am interested in using this feature once it is available. Thanks! |
@astepe I ended up not having enough getting time to make much progress. I may try to give it a go in the future though |
sqlalchemy supports the array type for postgress
https://docs.sqlalchemy.org/en/13/core/type_basics.html#sqlalchemy.types.ARRAY
would be mapped from openapi
array
typehttps://swagger.io/docs/specification/data-models/data-types/#array
happy to submit a pr for this if you think its worth it
The text was updated successfully, but these errors were encountered: