We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Would be great if we improve the behavior of herbs update for cases when entities have relationship with other entities.
herbs update
entity('ToDoList', { id: field(Number), items: field(Item),
This should create a migration with:
return knex.schema .createTable('ToDoList', function (table) { table.string('id').primary() table.string('itemId').references('id').inTable('Item') })
entity('ToDoList', { id: field(Number), items: field([Item]),
return knex.schema .createTable('ToDoList', function (table) { table.string('id').primary() ... }) .alterTable('Item', function (table) { table.string('itemId').references('id').inTable('ToDoList') ... })
The text was updated successfully, but these errors were encountered:
@endersoncosta is working on it PR: #144
Sorry, something went wrong.
No branches or pull requests
Would be great if we improve the behavior of
herbs update
for cases when entities have relationship with other entities.one-to-one
This should create a migration with:
one-to-many
This should create a migration with:
The text was updated successfully, but these errors were encountered: