Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nxlV3-0004Pi-J1 for pgsql-docs@arkaria.postgresql.org; Sun, 05 Jun 2022 08:20:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nxlV0-0006tL-QV for pgsql-docs@arkaria.postgresql.org; Sun, 05 Jun 2022 08:20:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nxlV0-0006tC-Gs for pgsql-docs@lists.postgresql.org; Sun, 05 Jun 2022 08:20:38 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nxlUy-0001ap-KA for pgsql-docs@postgresql.org; Sun, 05 Jun 2022 08:20:37 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id v106so20859020ybi.0 for ; Sun, 05 Jun 2022 01:20:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=roji.org; s=roji; h=mime-version:from:date:message-id:subject:to; bh=BXYdwBrthr5rRCXimBFBqZAFtx/VSYu01gU0wSnZh/o=; b=V6k0ASZKy6qb8kY0QAftCatYrMUePXtVwv72W+ElLLaC6Khc5I70+KA5TNXj5j6sos gwgODgd1vcGKF5RsW7nTgd9TGk+ml0Urax/m8PpYDR45gm2c53J6KNn1VduHZYE4YVlP 1YqvU9pkeVNumwv8Mg9/wFLNVlLCBtI6RZCH0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=BXYdwBrthr5rRCXimBFBqZAFtx/VSYu01gU0wSnZh/o=; b=gCfy2A6LPA4xGzn2xyZLh/rC61TqkEjNRJTVyMYKagcd0Ic0tWJ80FydZZQTPzWA5C 1ZIwrASnoHekYxkIElP38Awt+09ZiLkdeuTOqAevqKsxcfgjcy618cBzAL7c6rsct3af Agf0bpFLTv49/Ci70oI5rUzVht3iiQg2CeNgkb5ojol19s6tvVpB6YHSSj0YRV5DQ+xR fdTI56zkmXtbOChxLLciNKa3t/y1+T/8rmJ6aDVxAILWh2qdvO1MxC4zS9nsNOXPML6T aw3fMcXHakk7oUZYcRoEd48WfuvnVfkFiCZOgsP3inrO1dxR6hr0YC+9YTG4PYEjcfhP AdKw== X-Gm-Message-State: AOAM530vGoMmxdzGR6vgwyQreFJOpkGRsM98dzyr1vMPQqnrJV72IZSW MlUcoq5rMOQamzNWr2rYG32jfagIaq+Ew+0kI4ARb6vgnkw5pw== X-Google-Smtp-Source: ABdhPJy01IIZn2Px1FB4S8EDrm0hzbnPF8gBGJ8ZLmFComP7XJlIklTas3O1Mrejfj8RPy71Kj10KdOUPNYMmbzDCFQ= X-Received: by 2002:a5b:148:0:b0:650:15bd:97ab with SMTP id c8-20020a5b0148000000b0065015bd97abmr19349569ybp.231.1654417234430; Sun, 05 Jun 2022 01:20:34 -0700 (PDT) MIME-Version: 1.0 From: Shay Rojansky Date: Sun, 5 Jun 2022 10:20:23 +0200 Message-ID: Subject: Lower/upper-case consistency with function names To: pgsql-docs@postgresql.org Content-Type: multipart/alternative; boundary="00000000000091a39d05e0af07e8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000091a39d05e0af07e8 Content-Type: text/plain; charset="UTF-8" Hi all, The PostgreSQL docs mostly show function names in lowercase (e.g. [1], [2]), which seems to be the PostgreSQL-idiomatic thing to do. However, some pages show functions in upper case, e.g. COALESCE/NULLIF/GREATEST/LEAST ([3]). Is there some difference between these which warrants the case difference, or just a case of docs inconsistency? I ran into this while trying to make Entity Framework (.NET ORM) generate more idiomatic-looking SQL. If this is just an inconsistency, it's obviously not very important. Thanks, Shay [1] https://www.postgresql.org/docs/current/functions-aggregate.html [2] https://www.postgresql.org/docs/current/datatype-datetime.html [3] https://www.postgresql.org/docs/current/functions-conditional.html --00000000000091a39d05e0af07e8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

The PostgreSQL docs mostly show= function names in lowercase (e.g. [1], [2]), which seems to be the Postgre= SQL-idiomatic thing to do. However, some pages show functions in upper case= , e.g. COALESCE/NULLIF/GREATEST/LEAST ([3]). Is there some difference betwe= en these which warrants the case difference, or just a case of docs inconsi= stency?

I ran into this while trying to make Entit= y Framework (.NET ORM) generate more idiomatic-looking SQL. If this is just= an inconsistency, it's obviously not very important.