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
When I add models, commands, or relationships, I want to ignore a certain target.
For example, let's say I use an ORM-managed migration (e.g. drizzle-kit).
It creates a table __drizzle_migrations in schema drizzle.
And ddn cli cares it when I execute these.
Thank you for this interesting suggestion. We have added this to our backlog. In the meantime, you can try out the following workflow:
Use ddn model add <connector> "*" to track all the models and then do ddn model remove <pattern-for-model-names> to remove the ones you don't want to be tracked. (Note: ddn model remove command is available from DDN CLI version v2.12.0)
In your case, models generated from schema drizzle will usually have the prefix as drizzle. So your command might be something like ddn model add <connector> "*" && ddn model remove "drizzle*".
You can also add this as a custom script with a name like add-models-ignoring-drizzle which can be invoked as ddn run add-models-ignoring-drizzle as a quick way to invoke this quickly in your regular dev workflow.
Component
c/v3-cli
Is your proposal related to a problem?
When I add models, commands, or relationships, I want to ignore a certain target.
For example, let's say I use an ORM-managed migration (e.g. drizzle-kit).
It creates a table
__drizzle_migrations
in schemadrizzle
.And
ddn
cli cares it when I execute these.Though I can specify whitelist instead of
"*"
, it's too cumbersome.Describe the solution you'd like
The text was updated successfully, but these errors were encountered: