You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Anytime I see migrations like 0001, 0002, ..., 0313 I don't know what's going on. I think migrations should be additionally grouped by deployment, like cassandra. Greate source for this is temporal schema. I just want to let you know about this because I was sitting on this recently and grouping by deployment is missing piece frmo all these frameworks, across the board.
Another idea is putting custom operations with migrations - whenever migrations are being run in many cases there is some data meddling. This is best illustrated with django migrations. Just throwing it out there - not sure if you are aware of it, or even if you have this developer workflow integrated into your structure to be honest.
This is just a quick note to you guys, because I just found about you from twitter and your project looks promising. I am using mikro-orm for migration generation and kysely-codegen for getting something better than knex.
PS. you can also consider having ContentType table. It is one thing which is missing from js/ts ecosystem as far as I am aware. Having it allows for generic relations, without custom enum fields which has to be mapped to tables anyway.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Anytime I see migrations like 0001, 0002, ..., 0313 I don't know what's going on. I think migrations should be additionally grouped by deployment, like cassandra. Greate source for this is temporal schema. I just want to let you know about this because I was sitting on this recently and grouping by deployment is missing piece frmo all these frameworks, across the board.
Another idea is putting custom operations with migrations - whenever migrations are being run in many cases there is some data meddling. This is best illustrated with django migrations. Just throwing it out there - not sure if you are aware of it, or even if you have this developer workflow integrated into your structure to be honest.
This is just a quick note to you guys, because I just found about you from twitter and your project looks promising. I am using mikro-orm for migration generation and kysely-codegen for getting something better than knex.
PS. you can also consider having ContentType table. It is one thing which is missing from js/ts ecosystem as far as I am aware. Having it allows for generic relations, without custom enum fields which has to be mapped to tables anyway.
Beta Was this translation helpful? Give feedback.
All reactions