| From: | "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | Benjamin Scherrey <scherrey(at)proteus-tech(dot)com>, pgsql-www(at)lists(dot)postgresql(dot)org, Vik Fearing <vik(at)postgresfriends(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Describing Postgres as "object-relational" on the home page |
| Date: | 2024-01-01 20:15:16 |
| Message-ID: | 20240101141516.5a9274ee@slate.karlpinc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Mon, 1 Jan 2024 13:44:59 -0600
"Karl O. Pinc" <kop(at)karlpinc(dot)com> wrote:
> instead of coming up with wording describing
> functionality, workloads, etc., to simply say "PostgrSQL does lots
> more stuff." on the home page and link that to a page with nothing
> but keywords.
> To extend this idea, just a list of keywords is not engaging.
> Categorizing the keywords by attaching one or more tags to each opens
> up possibilities for interaction and alternate ways to view the
> keywords.
-- A back of the envelope schema for tagged technology keywords
CREATE TABLE keywords (
keyword TEXT PRIMARY KEY,
url TEXT,
cantag BOOLEAN);
CREATE TABLE taggings (
tag TEXT REFERENCES keywords,
keyword TEXT REFERENCES keywords);
-- And a trigger is needed to ensure that taggings.tag
-- is related to a keywords row having a keywords.cantag value of true.
Regards,
Karl <kop(at)karlpinc(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl O. Pinc | 2024-01-01 22:48:19 | Re: Describing Postgres as "object-relational" on the home page |
| Previous Message | Karl O. Pinc | 2024-01-01 19:44:59 | Re: Describing Postgres as "object-relational" on the home page |