From: | jian he <jian(dot)universality(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | refactor func-matching.sgml, make regexp* function more readable |
Date: | 2025-10-16 07:43:49 |
Message-ID: | CACJufxFuk9P=P4=BZ=qCkgvo6im8aL8NnCkjxx2S2MQDWNdouw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
hi.
https://www.postgresql.org/docs/current/functions-matching.html#FUNCTIONS-POSIX-REGEXP
section3 way too big.
The first big part is all these (regexp*) functions, the second part
is (9.7.3.1. Regular Expression Details )
Please check the attached refactoring. output sample picture also attached.
All these functions (regexp_count, regexp_instr, regexp_like, regexp_match,
regexp_matches, regexp_replace, regexp_split_to_array, regexp_split_to_table,
regexp_substr) are explained/described one after another, which makes the
section (9.7.3 first part) feels a bit condensed.
So I’ve split them up and enclosed each in its own <sect4> section.
I used <synopsis> to mark up each function’s syntax, followed by a detailed
description. Since each function’s explanation is quite long, using <sect4> to
separate them seems more reasonable.
we could use <table> to group them, like
https://www.postgresql.org/docs/current/functions-json.html#SQLJSON-QUERY-FUNCTIONS
but we have many functions here, using <sect4> would be better than <table>.
Attachment | Content-Type | Size |
---|---|---|
v1-0001-first-try-to-refactor-func-matching.sgml.patch | text/x-patch | 19.7 KB |
posix_regex_functions.png | image/png | 1.1 MB |
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2025-10-16 07:52:16 | Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement |
Previous Message | Michael Paquier | 2025-10-16 07:26:48 | Re: Improved TAP tests by replacing sub-optimal uses of ok() with better Test::More functions |