Is your feature request related to a problem? Please describe.
The Quark Server (the father of Quark Studio) was not protecting the Quark database, where access tokens was stored. It means that everyone with table.select permission could select tokens from there and get the access to all the databases, which was unacceptable.
Describe the solution you'd like
Private databases system solves this problem. To provide the protection from outside by querying, the database could be marked as private, so the Quark Cloud would response to queries using it as if the database did not exist at all!
Is your feature request related to a problem? Please describe.
The Quark Server (the father of Quark Studio) was not protecting the
Quarkdatabase, where access tokens was stored. It means that everyone withtable.selectpermission could select tokens from there and get the access to all the databases, which was unacceptable.Describe the solution you'd like
Private databases system solves this problem. To provide the protection from outside by querying, the database could be marked as private, so the Quark Cloud would response to queries using it as if the database did not exist at all!
create databasemust get a new parameterprivate (boolean) = falsedatabaseExistson private database name must returnfalseeven though it exists on the disk.privateDatabaseExistsmust be added. The name of the method may be changed.change visibility of <database name>: to = <visibility>;must be added. Consider the best permission option ("*"?)