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
While migrations generally touch only the Database schema, sometimes it's useful to be able to apply some data changes as well. For example, dropping the values in an old column or updating values for a new column based on data that already exists in the database.
It would be helpful if Hasura reported more information about the actual results of running SQL statements from the migrations for example the number of rows affected by a statement.
Attempting to include statements inside of a migration file that should explicitly return results (eg SELECT COUNT(*) FROM table;) do not produce any information in the migration logs even when running with --log-level DEBUG
The text was updated successfully, but these errors were encountered:
While migrations generally touch only the Database schema, sometimes it's useful to be able to apply some data changes as well. For example, dropping the values in an old column or updating values for a new column based on data that already exists in the database.
It would be helpful if Hasura reported more information about the actual results of running SQL statements from the migrations for example the number of rows affected by a statement.
Attempting to include statements inside of a migration file that should explicitly return results (eg
SELECT COUNT(*) FROM table
;) do not produce any information in the migration logs even when running with--log-level DEBUG
The text was updated successfully, but these errors were encountered: