Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iHBSG-0005Cx-1D for pgsql-docs@arkaria.postgresql.org; Sun, 06 Oct 2019 18:40:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iHBSD-0002wl-A7 for pgsql-docs@arkaria.postgresql.org; Sun, 06 Oct 2019 18:40:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iHBSD-0002wV-2l for pgsql-docs@lists.postgresql.org; Sun, 06 Oct 2019 18:40:25 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iHBSA-0004v0-Dn for pgsql-docs@lists.postgresql.org; Sun, 06 Oct 2019 18:40:24 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x96IeJQ4022504; Sun, 6 Oct 2019 14:40:19 -0400 From: Tom Lane To: zimtigerclaw@gmail.com cc: pgsql-docs@lists.postgresql.org Subject: Re: grammar mistake in java8-date-time.html ? In-reply-to: <157036414904.25290.2410205062464473656@wrigleys.postgresql.org> References: <157036414904.25290.2410205062464473656@wrigleys.postgresql.org> Comments: In-reply-to PG Doc comments form message dated "Sun, 06 Oct 2019 12:15:49 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22502.1570387219.1@sss.pgh.pa.us> Date: Sun, 06 Oct 2019 14:40:19 -0400 Message-ID: <22503.1570387219@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Doc comments form writes: > I think that there's a grammar error in the following doc url: > https://jdbc.postgresql.org/documentation/head/java8-date-time.html > It says: "Also note that all OffsetDateTime instances will have be in UTC > (have offset 0)." > I suspect that it was supposed to read: "will be". You'd need to report this to the JDBC project --- this list is just for documentation issues in core Postgres. regards, tom lane