Skip to content

Commit

Permalink
Add ef migrations for sql databases
Browse files Browse the repository at this point in the history
OpenIdDict 5.0 introduces some model changes. Hence, we need ef migrations to make changes to the database. Version 2 of pixel identity did not use migrations and auto created database. Starting next version, pixel-identity will require that database tables are generated first by running migration sqls.
  • Loading branch information
Nfactor26 committed Jan 20, 2024
1 parent 1cee63a commit f00a112
Show file tree
Hide file tree
Showing 17 changed files with 4,170 additions and 1 deletion.
16 changes: 15 additions & 1 deletion Pixel.Identity.sln
Original file line number Diff line number Diff line change
Expand Up @@ -42,13 +42,15 @@ EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "workflows", "workflows", "{1872169C-F107-43FD-AE02-6DDF88241644}"
ProjectSection(SolutionItems) = preProject
.github\workflows\identity-build-and-test-docker.yaml = .github\workflows\identity-build-and-test-docker.yaml
.github\workflows\identity-build-only.yaml = .github\workflows\identity-build-only.yaml
.github\workflows\identity-build-docker-image.yaml = .github\workflows\identity-build-docker-image.yaml
.github\workflows\identity-build-only.yaml = .github\workflows\identity-build-only.yaml
.github\workflows\identity-publish-to-docker-hub.yaml = .github\workflows\identity-publish-to-docker-hub.yaml
.github\workflows\identity-test-docker-image-with-mongo.yaml = .github\workflows\identity-test-docker-image-with-mongo.yaml
.github\workflows\identity-test-docker-image-with-postgres.yaml = .github\workflows\identity-test-docker-image-with-postgres.yaml
EndProjectSection
EndProject
Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "Pixel.Identity.Store.Sql.Migrations", "src\Pixel.Identity.Store.Sql.Migrations\Pixel.Identity.Store.Sql.Migrations.csproj", "{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}"
EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Debug|Any CPU = Debug|Any CPU
Expand Down Expand Up @@ -239,6 +241,18 @@ Global
{440B2ECE-5DCF-481D-9C18-0EC8F4F18E98}.Release|x64.Build.0 = Release|Any CPU
{440B2ECE-5DCF-481D-9C18-0EC8F4F18E98}.Release|x86.ActiveCfg = Release|Any CPU
{440B2ECE-5DCF-481D-9C18-0EC8F4F18E98}.Release|x86.Build.0 = Release|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Debug|Any CPU.Build.0 = Debug|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Debug|x64.ActiveCfg = Debug|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Debug|x64.Build.0 = Debug|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Debug|x86.ActiveCfg = Debug|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Debug|x86.Build.0 = Debug|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Release|Any CPU.ActiveCfg = Release|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Release|Any CPU.Build.0 = Release|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Release|x64.ActiveCfg = Release|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Release|x64.Build.0 = Release|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Release|x86.ActiveCfg = Release|Any CPU
{88822DEF-9DEA-4E61-8DAE-DF387C904A1F}.Release|x86.Build.0 = Release|Any CPU
EndGlobalSection
GlobalSection(SolutionProperties) = preSolution
HideSolutionNode = FALSE
Expand Down
Loading

0 comments on commit f00a112

Please sign in to comment.