In the most 2016 update the relative says it's common to see weird effects from the spools. If it's so common it should be reproducible I would think, yet I've never seen it done.
Please don't think that I'm trying to suggest... anything . It's just that I'm getting used to read this pattern in the output of LLMs. "While this and that is great...". Maybe we're mimicking them now? I catch myself using these disclaimers even in spoken language.
When I need to add new data to a table I have, I just put the "new_column Type" in my prisma.schema for table X. and run "npx prisma migrate dev." Then everywhere else in my code, I already have the updated type for my object X.new_column and can access it with the guardrails of not betraying what type it is.
I'd rather do that than ALTER TABLE to create and update my read queries, while making sure I don't make a mistake in the raw SQL.
And migrations are a separate feature that a number of ORMs have, you can have clean migrations with pure SQL using a tool like gomigrate.
I think the real utility is that the ORM is doing the marshalling for you.
I always feel like I'm missing something because it looks like you have to learn a specific library instead of a general purpose language.
Especially now with the new template syntax, signals, and other recent changes.
Looks like some work needs to be done to get this into familiar CAD terms with the English translation.
Difficult to use right now, it just switched into the Chinese translation when trying to make a cube and there doesn't appear to be an easy way to change that.