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 1rICpU-006yV0-Rw for pgsql-www@arkaria.postgresql.org; Tue, 26 Dec 2023 19:11:04 +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 1rICpT-00EqfI-8R for pgsql-www@arkaria.postgresql.org; Tue, 26 Dec 2023 19:11:03 +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 ) id 1rICpT-00Eqf5-1Q for pgsql-www@lists.postgresql.org; Tue, 26 Dec 2023 19:11:03 +0000 Received: from janus.karlpinc.com ([173.161.46.12] helo=smtp.karlpinc.com) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rICpP-00E1Ky-LJ for pgsql-www@lists.postgresql.org; Tue, 26 Dec 2023 19:11:02 +0000 Received: from slate.karlpinc.com (unknown [192.168.1.14]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp.karlpinc.com (Postfix) with ESMTPS id 5C9A3A6CE for ; Tue, 26 Dec 2023 13:10:51 -0600 (CST) Received: from slate.karlpinc.com (localhost [IPv6:::1]) by slate.karlpinc.com (Postfix) with ESMTPS id 1C9743FB4D for ; Tue, 26 Dec 2023 13:10:51 -0600 (CST) Date: Tue, 26 Dec 2023 13:10:47 -0600 From: "Karl O. Pinc" To: pgsql-www@lists.postgresql.org Subject: Describing Postgres as "object-relational" on the home page Message-ID: <20231226131047.493259f8@slate.karlpinc.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, I don't want to start bikeshedding here but maybe the answer is simple. The PG home page calls PG "object-relational". I question whether this is useful. Unlike in the 90's, nobody is really interested any more in object-oriented-everything and the typical person reading the home page probably does not know what an object-relational db is anyway. It may be better to just say "relational". In my opinion simpler is more clear and therefore better. (If another adjective is necessary I like "advanced". I feel it balances "powerful" and, in a sense, substitutes for the "object" qualifer. Because PG is more than just object-relational.) I am only asking whether the home page should be changed. Changing the "object-relational" description elsewhere/everywhere is another matter entirely. I suppose I think this because I think the home page has a different, less sophisticated, audience. For my off-the-cuff mini-rant on this topic see the PostgeSQL Wikipedia talk page: Describing PG as relational v.s. object-relational in the lead https://en.wikipedia.org/wiki/Talk:PostgreSQL#Describing_PG_as_relational_v.s._object-relational_in_the_lead FWIW, I know of at least 4 toggles between "relational" and "object-relational" on the wikipedia page. (It's been just "relational" for some time, but recently toggled back and forth. Feel free to explain on the talk page and change it from the current "relational" to "object-relational". I won't undo. I wrote the talk page entry mostly to keep the postgres-ignorant wikipedia enthusiasts from copy-pasting from the PG home page.) This is not worth spending much time on but I wanted to raise the issue, hoping it can be quickly resolved. There seems to be no discussion in the pgsql-www mailing list archive. Regards, Karl Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein