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 think #3606 is sort of related to this issue, but what they're asking for there is much more complex. I just want a way to omit the schema prefix on table names.
Describe alternatives you've considered
None that I'm aware, I think the prefix is unavoidable.
The text was updated successfully, but these errors were encountered:
Is your proposal related to a problem?
Using a schema besides
public
results in all tables having a prefix, likemyschema_mytable
.Describe the solution you'd like
If you connect to the database specifying a search_path, the first schema should be prefixless. For example:
In this case, any table from the
processor
schema should have no prefix.I see in this response to #3606 that the proposed solution is to use Hasura DDN. However DDN is lacking many features I need at the moment: https://hasura.io/docs/3.0/upgrade/feature-availability/api-features/. I also can't find any docs describing how to migrate from v2 to DDN in terms of just the metadata file.
I think #3606 is sort of related to this issue, but what they're asking for there is much more complex. I just want a way to omit the schema prefix on table names.
Describe alternatives you've considered
None that I'm aware, I think the prefix is unavoidable.
The text was updated successfully, but these errors were encountered: