Diplomarbeit-Absolventenverein/oqtane.framework
6
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

improve error handling for the scenario where a connection string does not exist in appsettings.json for a tenant

Browse Source
This commit is contained in:
sbwalker
2025-08-14 15:57:50 -04:00
parent b5a9c32c3e
commit 4ab8f8cc25
1 changed files with 13 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
Oqtane.Server/Infrastructure/DatabaseManager.cs
View File

@ -392,11 +392,20 @@ namespace Oqtane.Infrastructure
tenant.DBConnectionString = MigrateConnectionString(db, tenant);
try
{
using (var tenantDbContext = new TenantDBContext(DBContextDependencies))
var connectionString = _configManager.GetSetting($"{SettingKeys.ConnectionStringsSection}:{tenant.DBConnectionString}", "");
if (!string.IsNullOrEmpty(connectionString))
{
AddEFMigrationsHistory(sql, _configManager.GetSetting($"{SettingKeys.ConnectionStringsSection}:{tenant.DBConnectionString}", ""), tenant.DBType, tenant.Version, false);
// push latest model into database
tenantDbContext.Database.Migrate();
using (var tenantDbContext = new TenantDBContext(DBContextDependencies))
{
AddEFMigrationsHistory(sql, connectionString, tenant.DBType, tenant.Version, false);
// push latest model into database
tenantDbContext.Database.Migrate();
}
}
else
{
result.Message = "A Connection String Named " + tenant.DBConnectionString + " Does Not Exist For Tenant " + tenant.Name + " In The ConnectionStrings Section Of Appsettings.json";
_filelogger.LogError(Utilities.LogMessage(this, result.Message));
}
}
catch (Exception ex)