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
Que inserts and reads jobs in the public schema by default (see this example in the source), but que-web does not mention the schema in queries. This conflicts with multi-tenancy rack middleware like apartment.
Would it be problematic to specify the DB schema in all SQL queries?
The text was updated successfully, but these errors were encountered:
guilherme-andrade
changed the title
Support Multitenanted schemas by adding public. to all SQL queries to que_jobs
Support Multitenanted schemas
Jan 21, 2021
Que inserts and reads jobs in the public schema by default (see this example in the source), but que-web does not mention the schema in queries. This conflicts with multi-tenancy rack middleware like apartment.
Would it be problematic to specify the DB schema in all SQL queries?
If que writes to public I think adding the schema in que-web makes sense.
Que inserts and reads jobs in the
public
schema by default (see this example in the source), butque-web
does not mention the schema in queries. This conflicts with multi-tenancy rack middleware like apartment.Would it be problematic to specify the DB schema in all SQL queries?
The text was updated successfully, but these errors were encountered: