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
New database support usually involves the following steps:
Create a new project (e.g. FluentMigrator.Runner.Snowflake) and copy all code from the database that is compatible with Snowflake.
Add unit tests for the generated syntax (found under Unit/Generators in the test project)
Add integration unit tests (found under Integration/Processors in the test project)
Add an example connection string to appsettings.json for the test project
Maybe a small comment what's the easiest to test this database during FluentMigrator development
Some databases contain features that aren't covered by FluentMigrator by default. The code to use these features (from your migration) needs to be put into a separate FluentMigrator.Extensions.Snowflake assembly. The extensions are the consumed/processed by the Snowflake processor. We already have extension assemblies for Oracle, SQL Anywhere and the SQL Server.
The text was updated successfully, but these errors were encountered:
@fubar-coder I'm very close to closing out all active issues in this repository, but this one is a pretty big lift.
Would you have any interest in writing an article for this, and perhaps merging the Snowflake existing logic into the master branch of fluentmigrator/fluentmigrator? If not, no big deal... just thought I would ask.
From the Gitter chat:
New database support usually involves the following steps:
FluentMigrator.Runner.Snowflake
) and copy all code from the database that is compatible with Snowflake.Unit/Generators
in the test project)Integration/Processors
in the test project)appsettings.json
for the test projectSome databases contain features that aren't covered by FluentMigrator by default. The code to use these features (from your migration) needs to be put into a separate
FluentMigrator.Extensions.Snowflake
assembly. The extensions are the consumed/processed by the Snowflake processor. We already have extension assemblies for Oracle, SQL Anywhere and the SQL Server.The text was updated successfully, but these errors were encountered: