-
Notifications
You must be signed in to change notification settings - Fork 22
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
🌟 [WIP] DB Migration Tool #487
base: main
Are you sure you want to change the base?
Conversation
Coverage Report
Click to view remaining coverage report
|
visit: commandModule => commandModule.default, | ||
}), | ||
// eslint-disable-next-line @typescript-eslint/no-empty-function | ||
handler: () => {}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's the plan here ?
name: { | ||
default: "", | ||
type: "string", | ||
description: "Entity name to migrate", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think migrations should be per-entity, they can mutate together inter-dependently, I propose we remove the option all together. If we want a limit in migrations it should be per version thereof
decimal: "numeric", // Assuming decimal numbers are stored as numeric in PostgreSQL | ||
encoded_json: "text", // Assuming encoded JSON objects are stored as text in PostgreSQL | ||
}; | ||
console.log("\n ##################################### \n"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this feels like something that would be in the pgsql adapter
No description provided.