From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp21.mail.ru (smtp21.mail.ru [94.100.179.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 7F1CE469719 for ; Thu, 12 Mar 2020 18:04:06 +0300 (MSK) Date: Thu, 12 Mar 2020 15:04:04 +0000 From: Nikita Pettik Message-ID: <20200312150404.GA4065@tarantool.org> References: <20200309150258.32584-1-roman.habibov@tarantool.org> <6B917D0D-6B5F-4CC3-A7ED-43B0768B2537@tarantool.org> <83e93b75-de08-865d-a8c2-9e899e27cc09@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <83e93b75-de08-865d-a8c2-9e899e27cc09@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH] sql: use unify pattern for column names List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org On 12 Mar 01:14, Vladislav Shpilevoy wrote: > Hi! Thanks for the patch! > > > sql: use unify pattern for column names > > > > Name resulting columns generated by an expression or > > construction by the "_COLUMN_N" pattern. > > 1. I would use 'COLUMN_N', without leading '_', which usually > means something internal, not intended for being used by users. > But even better option - ask Nikita. I'm okay with both options. > > Closes #3962 > > > > @TarantoolBot document > > Title: Column naming in SQL > >