From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 216412C142 for ; Tue, 7 May 2019 12:41:05 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id txrdgXu8q_wS for ; Tue, 7 May 2019 12:41:04 -0400 (EDT) Received: from smtp51.i.mail.ru (smtp51.i.mail.ru [94.100.177.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id A2A9F2A29A for ; Tue, 7 May 2019 12:41:04 -0400 (EDT) Date: Tue, 7 May 2019 19:41:02 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [PATCH v1 1/1] sql: replace schema_find_id() by box_space_id_by_name() Message-ID: <20190507164102.GD10365@atlas> References: <46e305e6bbce44d3a785963a58135d9efa425bdb.1556377851.git.imeevma@gmail.com> <642C2122-385A-4FBB-86DB-DB75E77081E6@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <642C2122-385A-4FBB-86DB-DB75E77081E6@tarantool.org> Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: tarantool-patches@freelists.org Cc: Imeev Mergen * n.pettik [19/05/07 19:21]: > > > +-- Ensure that the CREATE TRIGGER statement cannot be executed if > > +-- the user does not have enough rights. In this case, the user > > +-- does not have rights to read from _space. > > +-- > > +box.execute([[CREATE TRIGGER r1 AFTER INSERT ON t1 FOR EACH ROW BEGIN SELECT 1; END; ]]) > > +--- > > +- error: Space 'T1' does not exist > > Such error looks a bit confusing IMHO. Could we tell the absence > of space from lack of rights? It's OK to produce a confusing error message for a user which has no access to a space. This message is just fine. We should just be consistent and not reveal that the space exists through the error message. -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32