Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1saQMH-008iVm-30
	for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Aug 2024 01:48:29 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1saQMD-007Xrd-6U
	for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Aug 2024 01:48:25 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <ishii@postgresql.org>)
	id 1saQMC-007XrU-NP
	for pgsql-hackers@lists.postgresql.org; Sun, 04 Aug 2024 01:48:24 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by magus.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <ishii@postgresql.org>)
	id 1saQMA-00311F-1O
	for pgsql-hackers@lists.postgresql.org; Sun, 04 Aug 2024 01:48:23 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type:
	Mime-Version:From:Subject:To:Message-Id:Date:Sender:Reply-To:Cc:Content-ID:
	Content-Description:In-Reply-To:References;
	bh=qUOnA3YleyPzbl8u6EYL5Pxw0yu8lfx4h1V6HCmqEhM=; b=bO8l4it92M7+sk075PcbRFvORx
	oqJ6uoe3MHCltDe/nAAQkW5gQISeYtVmiR1E2foZ7Obf0WMOXdh7sJvLULIvafYLmFYmyM8i8hJJh
	D8HP5P9YAundT45A58Wc/usgiqIH1qXZ+Kmjf5be8bVmO5VcYQGuzoDJ2hIIIfsLEsfe0lXmUPcrE
	gsLTvN56V1z68cvp5mPgXnRMMp2GW8sMS5TGoM8zoZAuZn6pR8qEN/gqUJg5vAt3GF8TJqGRMv7JM
	+WXkCwFDAvzMCR4IGCa+O8HdqIfyW6m7FX/9Mm5Ki/l1qKOlI7/uP4TnUq4ebn0PzvTP4VLi11BDL
	QqqfV1gA==;
Received: from [2409:11:4120:300:ed81:a0e8:a3a2:1055] (helo=localhost)
	by meldrar.postgresql.org with esmtpsa  (TLS1.3) tls TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
	(Exim 4.94.2)
	(envelope-from <ishii@postgresql.org>)
	id 1saQM6-007hec-N3
	for pgsql-hackers@lists.postgresql.org; Sun, 04 Aug 2024 01:48:21 +0000
Date: Sun, 04 Aug 2024 10:48:07 +0900 (JST)
Message-Id: <20240804.104807.1230474056016095674.ishii@postgresql.org>
To: pgsql-hackers@lists.postgresql.org
Subject: subquery and sub-SELECT
From: Tatsuo Ishii <ishii@postgresql.org>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:ed81:a0e8:a3a2:1055 (failed)
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/20240804.104807.1230474056016095674.ishii%40postgresql.org>
Precedence: bulk

In our documentations, "subquery", "sub-query", "sub-select" and
"sub-SELECT" are used. In English, are they interchangeable?  I am
asking because we are looking for Japanese translations for the
words. If they have the identical meaning in English, we can choose
single Japanese word for them. If not, we would like to use different
Japanese words to reflect the difference.

I noticed that "sub-SELECT" only appears in syntax rules in the
reference manuals. Maybe "sub-SELECT" should be tread differently from
others?

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp