Duplicate tables & relationships between public & tenant postgres schemas about apartment HOT 2 CLOSED

Ya I've been wanting to remove tenanted tables from public and vice versa
for a while but hadn't really thought about the best way to do it. I'd be
interested in seeing your implementation. Associations should still work
fine though given that public is hard coded onto the db's name. But I like
the idea of maintaining a clean public and always keeping it in the search
path. It certainly wouldn't work to add public to the persistent schemas
given the current implementation.

I'm not sure this would even need to be a config option, I'd just like it
to be standard. Happy to review a pull request if you're interested

brad

(on my phone)

In our in-house multi-tenant system, we overwrote several of the rails db
rake tasks so that we don't have duplicate tables between public and tenant
postgres schemas. We dump the SQL schemas into two files (one for public,
one for tenant). We also usually include public in the postgres schema
search path. This allows for active record associations to just work even
between the public & tenant postgres schemas.

It sounds like getting Apartment to work this way would require more than
just adding public to the persistent_schemas. Also, some of the other
Apartment issues sound related. Is this a configuration option that would
be valuable to add?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/46
.

from apartment.

I'm going to close this for now. It's something we're definitely aware of, but not currently a bug

from apartment.