Inconsistent behaviour between Ash.get and read actions, and Ash.load in context multitenancy (pg)
Ash.load(resource,[...], actor: user, tenant: company_id) works
Ash.get(resource, actor: user, tenant: company_id, load: [....]) doesnt work, same with custom read actions on resource
Is there some limitations with the context mulitenancy that i should be aware of? because i have struggled quite alot just loading relationships on resources, which should be one of the simplest things, but its not. I get wierd errors when i load with Ash.get or using custom read actions that there is not table like <UUID>.my_resource_table. It almost feels like it hits the wrong Repo or the wrong database. Im using two repos, but i just commented out the other repo from config and tried again, same error.
this is the error i get
any tips?
Ash.get(resource, actor: user, tenant: company_id, load: [....]) doesnt work, same with custom read actions on resource
Is there some limitations with the context mulitenancy that i should be aware of? because i have struggled quite alot just loading relationships on resources, which should be one of the simplest things, but its not. I get wierd errors when i load with Ash.get or using custom read actions that there is not table like <UUID>.my_resource_table. It almost feels like it hits the wrong Repo or the wrong database. Im using two repos, but i just commented out the other repo from config and tried again, same error.
this is the error i get
any tips?
Solution
@Zach Daniel ill mark it as solved, i dont have time to debug why it failed in the old project. Its working in the new project now.
