From: "n.pettik" <korablev@tarantool.org> To: tarantool-patches@freelists.org Cc: Imeev Mergen <imeevma@tarantool.org>, Konstantin Osipov <kostja@tarantool.org> Subject: [tarantool-patches] Re: [PATCH v1 1/1] sql: rework "no such object" and "object exists" errors Date: Fri, 15 Feb 2019 16:12:33 +0300 [thread overview] Message-ID: <1E5729AC-76AC-43BD-B7AD-871440316C17@tarantool.org> (raw) In-Reply-To: <20190215125007.GB14894@chai> > On 15 Feb 2019, at 15:50, Konstantin Osipov <kostja@tarantool.org> wrote: > > * n.pettik <korablev@tarantool.org> [19/02/15 15:46]: >>> + /*148 */_(ER_NO_SUCH_INDEX_NAME, "No index '%s' is defined in space '%s'") \ >> >> I’d better say ’No index with name …’. >> But it is to be discussed. > > It's a copycat of the INDEX_ID message. Yep, I've noticed this, but anyway. Without no difference between error messages user would wonder why in some cases name appears, and in other - id. IMHO. >>> /** >>> + * Increment error counter if error suppression isn't set. >>> + * >>> + * @param parse_context Current parsing context. >>> + */ >>> +void >>> +sql_parser_error(struct Parse *parse_context); >> >> I suggest to incapsulate call of diag set inside this >> function. To achieve this, lets make function take >> variadic params. It would allow us to reduce size >> of refactored code, at least. > > Nikita, I agree in general but given this entire function is > temporary, I think it's good enough. It is going to exist until we remove parse->nErr and parse->rc - long enough, I guess.
prev parent reply other threads:[~2019-02-15 13:12 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-15 10:06 [tarantool-patches] " imeevma 2019-02-15 12:44 ` [tarantool-patches] " n.pettik 2019-02-15 12:50 ` Konstantin Osipov 2019-02-15 13:12 ` n.pettik [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=1E5729AC-76AC-43BD-B7AD-871440316C17@tarantool.org \ --to=korablev@tarantool.org \ --cc=imeevma@tarantool.org \ --cc=kostja@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH v1 1/1] sql: rework "no such object" and "object exists" errors' \ /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