feat(cli): add "name" and "custom" arguments for db generate cli command#816
Merged
atinux merged 6 commits intonuxt-hub:mainfrom Feb 6, 2026
Merged
Conversation
|
@branislavjuhaas is attempting to deploy a commit to the NuxtLabs Team on Vercel. A member of the Team first needs to authorize it. |
branislavjuhaas
changed the title
onmax
reviewed
Feb 2, 2026
atinux
approved these changes
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds
nameandcusomflags support fornuxt db generatewhich under the hood usesdrizzle-kit generate. It also updates docs to mention these new options and provides consistency fix fornuxt db mark-as-migratedcommand'snameargument.Why to add this?
nameargument: When generating database migrations, it is a good practice to provide clear name describing the changes for better predictability of changes in devops environment. Providing option to do so is a good practice.customargument: There shall exist a way to generate empty sql migration file for more advanced database migrations. This is often necessary when installing postgres extensions, creating custom sql functions (e. g. immutable wrappers for extensions) or seeding the database.Fixes #815