Re:Django Styleguide
by rowanseymour on Wednesday January 11, 2023 @11:00AM
(#34339884)
Same here. If I was starting a non-Python project tomorrow I'd consider using Django to manage the database schema - especially now that we can describe custom indexes and constraints in migrations. Our project has gone thru over 1000 migrations so far tho we squash them down to 50 or so about once a year.
[ Parent
| on HN ]
Thats interesting, if I was using TypeScript to access the data, how would I keep the schemas in sync between TS and python?
Can introspect and export Django models to JSON schema or similar, then in TS read it and use compiler low-level API to generate types. There may be libraries for either stage…
Re:Django Styleguide
by rowanseymour on Wednesday January 11, 2023 @12:12PM
(#34341008)
I've never used TypeScript to talk to a database but there might be tooling to generate classes from tables. Even if there isn't, manually keeping some TypeScript classes in sync might still be worth the effort, for being able to manage schema migrations easily elsewhere.
We do this manually along with a pydantic as a middleman between Django and TS. Works pretty well and is not a major inconvenience to keep things aligned.
if using DRF you export openapi to json and use openapi-typescript-codegen
if using graphene or strawberry you export sdl to json and use @graphql-codegen/typescript
Re:Django Styleguide
by crucialfelix on Wednesday January 11, 2023 @03:02PM
(#34343810)
Prisma works very well and has usable migrations. Not as solid as Django's.
Tiangolo of FastAPI fame is working on https://sqlmodel.tiangolo.com/ Which is pydantic models, SQL alchemy. Migrations are coming soon. This will probably be an excellent way to build APIs with db. Then you can generate a typescript client from the built in OpenAPI schema.