From: Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: imeevma@tarantool.org Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v2 2/4] sql: properly show values in type mismatch error Date: Thu, 8 Jul 2021 00:09:57 +0200 [thread overview] Message-ID: <281c365c-afe9-0c36-526b-f9edb27452d2@tarantool.org> (raw) In-Reply-To: <73484ddc21ae698409d326804b105e748e3bbe12.1625498636.git.imeevma@gmail.com> Thanks for the patch! > diff --git a/src/box/sql/mem.c b/src/box/sql/mem.c > index 630f1a135..728d3c9a7 100644 > --- a/src/box/sql/mem.c > +++ b/src/box/sql/mem.c > @@ -80,9 +80,11 @@ mem_str(const struct Mem *mem) > if (mem->n > STR_VALUE_MAX_LEN) { > memcpy(buf, mem->z, STR_VALUE_MAX_LEN); > buf[STR_VALUE_MAX_LEN] = '\0'; > - return tt_sprintf("%s...", buf); > + return tt_sprintf("'%s...", buf); Why didn't you put a second ' after ...? The error message does not end here. There are more words after this string usually. The same below. > @@ -102,7 +115,8 @@ mem_str(const struct Mem *mem) > return tt_sprintf("%s...", buf); > } > case MEM_TYPE_UUID: > - return tt_uuid_str(&mem->u.uuid); > + tt_uuid_to_string(&mem->u.uuid, buf); > + return tt_sprintf("'%s'", buf); > case MEM_TYPE_BOOL: > return mem->u.b ? "TRUE" : "FALSE"; > default:
next prev parent reply other threads:[~2021-07-07 22:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-05 15:27 [Tarantool-patches] [PATCH v2 0/4] sql: fix description of " Mergen Imeev via Tarantool-patches 2021-07-05 15:27 ` [Tarantool-patches] [PATCH v2 1/4] sql: truncate values in " Mergen Imeev via Tarantool-patches 2021-07-07 22:09 ` Vladislav Shpilevoy via Tarantool-patches 2021-07-12 8:50 ` Mergen Imeev via Tarantool-patches 2021-07-05 15:27 ` [Tarantool-patches] [PATCH v2 2/4] sql: properly show " Mergen Imeev via Tarantool-patches 2021-07-07 22:09 ` Vladislav Shpilevoy via Tarantool-patches [this message] 2021-07-12 8:56 ` Mergen Imeev via Tarantool-patches 2021-07-05 15:27 ` [Tarantool-patches] [PATCH v2 3/4] sql: use proper type names in error descriptions Mergen Imeev via Tarantool-patches 2021-07-05 15:27 ` [Tarantool-patches] [PATCH v2 4/4] sql: make type mismatch error more informative Mergen Imeev via Tarantool-patches 2021-07-07 22:10 ` Vladislav Shpilevoy via Tarantool-patches 2021-07-12 8:58 ` Mergen Imeev via Tarantool-patches 2021-07-12 21:38 ` [Tarantool-patches] [PATCH v2 0/4] sql: fix description of type mismatch error Vladislav Shpilevoy via Tarantool-patches 2021-07-13 7:03 [Tarantool-patches] [PATCH v2 0/4] sql: fix description of type mismatch errors Mergen Imeev via Tarantool-patches 2021-07-13 7:03 ` [Tarantool-patches] [PATCH v2 2/4] sql: properly show values in type mismatch error Mergen Imeev via Tarantool-patches 2021-07-13 8:51 ` Timur Safin via Tarantool-patches
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=281c365c-afe9-0c36-526b-f9edb27452d2@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=imeevma@tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 2/4] sql: properly show values in type mismatch error' \ /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