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
Right now, when the specs of a Marten project are executed, the models of the project will be created at the database level once. Later on, if the same database is reused for running specs the same tables will be reused if they already exist. Model tables are created directly without running project migrations ; by default we should probably ensure that project migrations are used unless configured otherwise.
Let's introduce the ability to run project migrations when setuping spec databases while giving the ability to disable this behaviour through the use of a dedicated configuration option.
The text was updated successfully, but these errors were encountered:
Description
Right now, when the specs of a Marten project are executed, the models of the project will be created at the database level once. Later on, if the same database is reused for running specs the same tables will be reused if they already exist. Model tables are created directly without running project migrations ; by default we should probably ensure that project migrations are used unless configured otherwise.
Let's introduce the ability to run project migrations when setuping spec databases while giving the ability to disable this behaviour through the use of a dedicated configuration option.
The text was updated successfully, but these errors were encountered: