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 ) id 1s3ycl-00H4l4-PZ for pgsql-docs@arkaria.postgresql.org; Mon, 06 May 2024 13:43:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s3yci-00DHTO-7x for pgsql-docs@arkaria.postgresql.org; Mon, 06 May 2024 13:43:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s3ych-00DHTF-To for pgsql-docs@lists.postgresql.org; Mon, 06 May 2024 13:43:20 +0000 Received: from mout-u-107.mailbox.org ([2001:67c:2050:101:465::107]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s3ycf-001j90-RR for pgsql-docs@lists.postgresql.org; Mon, 06 May 2024 13:43:19 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:b231:465::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-107.mailbox.org (Postfix) with ESMTPS id 4VY2fl1BqCz9stK; Mon, 6 May 2024 15:43:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1715002991; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=vRAhkvXL3RGHuhtuGcbpenHKbVizpi3zyYeiKoYaIc0=; b=WpLmeHM7TTpzm7LIFx/AgLHfXhE54OqcBvW2TS7kOkIRGuX+O/c0qsDrIvn+W70u+d3yxl 5RkIH0iJFBWG75lLqeBzmgEiXODrK4ro3M1HaNbVLlHCN4NE5XIuYmRAnv6Ql0Gl57+VFO J+bVBWkDZfc5dh0sBJcWY4hBk1cTy6ZtrlsXO0fYF20BqPxoAPVOnhtHOtTL9q5X9DzRgF Jzm39esjpnz/tNgpTr4U+CpYjoh2rooLTPkKz2cmtAjuCDSVMpYFsgpc4oVyw4k7biJAB9 gWsU2Fu0WPb9PEqoY5IbPsSU300RKtjsSaXWyCCY3mkOC4Q7kO5Cc6oMT2yAyQ== Date: Mon, 6 May 2024 15:42:56 +0200 From: Erik Wienhold To: Alvaro Herrera Cc: David Rowley , Peter Eisentraut , pgsql-docs@lists.postgresql.org Subject: Re: nchar is undocumented Message-ID: <8ddac732-d650-4958-b9c9-ea8e6116251e@ewie.name> References: <202405060853.t3thj4gr4cpb@alvherre.pgsql> <202405060859.pxrknmug7hcg@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202405060859.pxrknmug7hcg@alvherre.pgsql> X-Rspamd-Queue-Id: 4VY2fl1BqCz9stK List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-05-06 10:59 +0200, Alvaro Herrera wrote: > By the way, this neighboring sentence is a bit awkward > > " It must be ... or a type for which there is a cast from json to that type." > > Would it be better to say > " It must be ... or a type to which a cast from json exists." > ? Yeah, that sounds better, but I'd say: "[...] or a type _for_ which a cast from json exists." Or maybe just "[...] or any type that can be cast to json." ? -- Erik