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 don't know if this is a bug or a feature request bug when I use config.excluded_models = ["User", "Company"], I expect the users and companies tables to NOT be created in any schema except the public schema.
In my case, I have a a lot of models that belong only in the public schema, so I end up with a lot of empty tables in all the other schemas (beside the public one).
The text was updated successfully, but these errors were encountered:
it's a known issue. Not a feature so much, we'd ideally like to avoid that, but haven't found the optimal solution yet. We're open to suggestions. It becomes more complicated because if you only had excluded models in public, then Rails can't generate the schema.rb file properly because it only sees those tables. Anyway it shouldn't cause any problems, it's just not ideal
I don't know if this is a bug or a feature request bug when I use
config.excluded_models = ["User", "Company"]
, I expect the users and companies tables to NOT be created in any schema except the public schema.In my case, I have a a lot of models that belong only in the public schema, so I end up with a lot of empty tables in all the other schemas (beside the public one).
The text was updated successfully, but these errors were encountered: