The following academic work (132 page pdf) elucidates this pattern in the context of a real application:
https://ris.utwente.nl/ws/portalfiles/portal/275963001/PDEng...
Using the expand and contract pattern for schema changes
41–45 of 45 posts
Re: Using the expand and contract pattern for schema changes
#42Earlier quoted context omitted.
Seems like you agree with my assessment.
:( Things can have similarities without being the same. Also not being unique is not a moral failure. I think I am failing to understand your stance.
Saying the pattern is the same isn't the same as saying two things fitting the pattern are the same in every respect.
Patterns are necessarily reductionist, like any sort of comparison of things that aren't 100% similar.
There is value in recognizing patterns. They're useful for comprehension and memory.
Re: Using the expand and contract pattern for schema changes
#43Earlier quoted context omitted.
:( Things can have similarities without being the same. Also not being unique is not a moral failure. I think I am failing to understand your stance.
Saying the pattern is the same isn't the same as saying two things fitting the pattern are the same in every respect. Patterns are necessarily reductionist, like any sort of comparison of things that aren't 100% similar. There is value in recognizing patterns. They're useful for comprehension and memory.
> This is the same pattern as versioning
I guess we disagree on the reasonable interpretations of this sentence
Re: Using the expand and contract pattern for schema changes
#44Earlier quoted context omitted.
Saying the pattern is the same isn't the same as saying two things fitting the pattern are the same in every respect. Patterns are necessarily reductionist, like any sort of comparison of things that aren't 100% similar. There is value in recognizing patterns. They're useful for comprehension and memory.
> This is the same pattern as versioning I guess we disagree on the reasonable interpretations of this sentence
That's only half of the sentence
Re: Using the expand and contract pattern for schema changes
#45I use Prisma on almost all my node.js projects these days, and I wish that part of schema migrations was also automated by Prisma. But last I checked, it doesn't even rename columns properly. I feel like maybe they should invest more R&D in their migrations technology? The ORM is pretty great.
What do you find good about Prisma?
The ORM is great! I usually setup my projects so the Prisma generated types are shared with the front end and build my own types on top of those.
I like the prisma schema first way of specifying my models too. It’s pretty intuitive and readable, it centralizes all my models in one place.
The migration system could be more advanced but does the job. Multiple production projects I worked heavily on use it.
Overall I think it’s very well designed software