From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Roman Khabibov <roman.habibov@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 0/2] add '_vcollation' sysview and fetch it in net.box
Date: Fri, 22 Mar 2019 18:39:53 +0300 [thread overview]
Message-ID: <20190322153953.GB6548@chai> (raw)
In-Reply-To: <20190322083348.aux2mcocsir3jxs2@esperanza>
* Vladimir Davydov <vdavydov.dev@gmail.com> [19/03/22 12:43]:
> On Fri, Mar 22, 2019 at 03:27:35AM +0300, Roman Khabibov wrote:
> > As I understood "readable for all" means that filter for
> > "_vcollation" must always return "true", because the condition
> > "User has read access to according system space" is always
> > met.
>
> Why not simply grant read acces to _collation to each user instead?
We discussed this with Roman and I asked him to create a view.
> Anyway, I don't understand why _collation space stores creator uid.
> What would we possibly need it for? Create a collation that is usable
> by one user, but not visible by others? It doesn't make any sense to me.
> I think that collations should only be created/modified/deleted by the
> admin, but allowed to be used by anyone...
In some databases collations are user-level objects. Basically,
owner id is there to not complicate our security model.
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov
prev parent reply other threads:[~2019-03-22 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 0:27 Roman Khabibov
2019-03-22 0:27 ` [PATCH 1/2] schema: add "_vcollation" sysview Roman Khabibov
2019-03-22 0:27 ` [PATCH 2/2] net.box: fetch '_vcollation' sysview into the module Roman Khabibov
2019-03-22 8:33 ` [PATCH 0/2] add '_vcollation' sysview and fetch it in net.box Vladimir Davydov
2019-03-22 15:39 ` Konstantin Osipov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190322153953.GB6548@chai \
--to=kostja@tarantool.org \
--cc=roman.habibov@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 0/2] add '\''_vcollation'\'' sysview and fetch it in net.box' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox