Right now we assume that saved queries only execute against the database they were saved in.
If the saved_queries table included a database column, a single database could be used to save queries against many other (potentially read-only) databases.
As part of this an optional plugin configuration can be used to specify which database the saved_queries table should live in, as opposed to now where it uses the first attached database.
Right now we assume that saved queries only execute against the database they were saved in.
If the
saved_queries
table included adatabase
column, a single database could be used to save queries against many other (potentially read-only) databases.As part of this an optional plugin configuration can be used to specify which database the
saved_queries
table should live in, as opposed to now where it uses the first attached database.