You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a database with different schemata, some belong to tenants, some not. To separate it better with Triplex, I am using the tenant_prefix config option. When I run Triplex.all() I'd expect to get only schemata which start with that configured prefix. But I just get all schemata in the database. I've noticed thatTriplex.exists?/1 takes the tenant_prefix into consideration.
The text was updated successfully, but these errors were encountered:
Hey @MMore, thanks for pointing that out. A PR for that is welcome. Also, you might want to check #74, and talk to @abarr, since he was working on some improvements to Triplex.all already.
Also, if you need to workaround it, you can use the config reserved_tenants to make sure that schema is not going to be created as well as not returned on Triplex.all
Hello!
I have a database with different schemata, some belong to tenants, some not. To separate it better with Triplex, I am using the
tenant_prefix
config option. When I runTriplex.all()
I'd expect to get only schemata which start with that configured prefix. But I just get all schemata in the database. I've noticed thatTriplex.exists?/1
takes thetenant_prefix
into consideration.The text was updated successfully, but these errors were encountered: