mudblazor and models

[abbadon1334]

"src/PolarisDesk.IdentityProvider/AspIdUsers.db" <-- will be in conflict on any future changes. I think the best solution is to remove it and add to gitignore and change reseeding method using the IS4 appsettings.json

[diego81b]

In my opinion the best way is to use Sql Server and the migration At least we can use the same database as the api server but with a different schema

[abbadon1334]

In my opinion the best way is to use SQL Server and the migration At least we can use the same database as the API server but with a different schema

if this is the way we must remove the SQLite file to avoid conflict and continue here the change of persistence.

For different schema you mean to use only for auth and ACL and the rest of the models in the API? I ask it only to better understand the dynamics behind

[diego81b]

In my opinion the best way is to use SQL Server and the migration At least we can use the same database as the API server but with a different schema

if this is the way we must remove the SQLite file to avoid conflict and continue here the change of persistence.

For different schema you mean to use only for auth and ACL and the rest of the models in the API? I ask it only to better understand the dynamics behind

For different schema I mean that default schema of migrations is dbo. So for a better mantainance of the db i suggest to use same db with: 1 - dbo schema for business model 2 - auth schema or similar for the use models

another point in favor of having the same db engine is the simplicity in using views, stored and permissions .

Last but not least Sqlite sucks

[valentinotheworld]

ok

[valentinotheworld]

riapro