That is correct, you did not suggest that you did recomend that approach but if you read the entire thread it was suggested by someone else at Volo and did resolve that issue, so it appears that the connectionstring naming is not consistant so I will have to accomodate for that however, the issue is still not resolved with the LanguageTexts error I indicated I am getting which only happens when I log in as a Tenant user. Host user works fine. Please read thread to understand the distribution of our host vs tenant tables.
Thanks.
Hi,
But it's been suggested here that I not use the connection name string, but rather use the full namespace and Interface class name to resolve this issue.
So how do I resolve the issue I'm getting as I've tried everything that's been suggested with no success.
That resolved the issue with the code not finding the Users table but now I get an error on the "LanguageTexts" table as shown below. Just to clarify all the ABP base tables, including Saas, Identity server, users, etc are in a 'host' DB and the only tables in the 'tenant' DB are our application specific tables. So I want all things ABP module(pro and otherwise) to look at the host DB.
I tried adding the following code to resolve that connection string, but it did not work,.
case "Volo.Abp.LanguageManagement.EntityFrameworkCore.ILanguageManagementDbContext":
using (_currentTenant.Change(null))
{
connectionstring = await base.ResolveAsync(connectionStringName);
}
break;
After looking at this deeper, what you suggested as the solution is not accurate. The 'connectionstringname' that is being used by the MultiTenantConnectionStringResolver are not the value you suggest, thus making it difficult to point each (if I choose to) module's DBContext to a particular connection string.
So to summarize I am trying to put all the ABP tables that store Identity, LanguageManagement, permissions, Auditing, users, etc into the Host's DB and just have tennat tables (application specific) in their own DB's for each tenant.
There is no clear direction in the documents or previous support tickets that outline this so an actual real world example of this being implemented using ABP would be much appreaciated.
Thank you. That resolves my issue
@gterdem
Is there a way to programitically set the abp.apppath?
Any update for this?
By the way, when I log in as a Host user I do not get an error. It's only when I log in as a Tenant user.
At the top of the DBContext class are the following class attributes which were put there by the generated ABP solution. With all the ABP module tables being in the one Host DB do I need to also put attribute lines in for each DBContext interface's from all the other modules as well?
[ReplaceDbContext(typeof(IIdentityProDbContext))]
[ReplaceDbContext(typeof(ISaasDbContext))]
[ConnectionStringName("Default")]
We have a Host DB that has all the Identity Server/Sass and CMS related tables. Each tennat has their own DB as specified in the TenantConnectionStrings table but we do not want the Users table in the Tenant DB. In the main DB context class of my project I have specified this setup with the following code.
However, when I log in via the Web Application as a Tenant user I get an error indicating that there is 'no relation to the users table'. I have stepped through the code and the logic to log into and set everything accordinly is working fine and against the users table in the host db (which has all users across all tenants) and is verified by a successful login result in the code. But there is some other logic somewhere that seems to be looking for the Users table in the Tenant DB which is why I believe I'm getting the error.
Can you tell me the best way to implement the configuration of having all these core tables in the Host DB and only Tenant specific tables (our application tables) in the individual tenant DB's?
Thanks.
