Re: proposal - function string_to_table - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal - function string_to_table
Date
Msg-id CAFj8pRD9cYeQGQCP=K8+m+zitRidb=+B3YD764bLYP65V4mXwQ@mail.gmail.com
Whole thread Raw
In response to Re: proposal - function string_to_table  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: proposal - function string_to_table  (Peter Smith <smithpb2250@gmail.com>)
List pgsql-hackers


po 24. 8. 2020 v 4:19 odesílatel Peter Smith <smithpb2250@gmail.com> napsal:
I have re-checked the string_to_table_20200821.patch.

Below is one remaining problem.

====

COMMENT (help text)

+        Splits the <parameter>string</parameter> at occurrences
+        of <parameter>delimiter</parameter> and forms the remaining data
+        into a table with one <type>text</type> type column.
+        If <parameter>delimiter</parameter> is <literal>NULL</literal>,
+        each character in the <parameter>string</parameter> will become a
+        separate element in the array.

Seems like here is a cut/paste error from the string_to_array help text.

"separate element in the array" should say "separate row of the table"

fixed


====

>>> Maybe a different choice of function name would be more consistent
>>> with what is already there?
>>> e.g.  split_to_table, string_split_to_table, etc.
>>
>> I don't agree. This function is twin (with almost identical behaviour) for "string_to_array" function, so I think so the name is correct.

OK

====

please, check attached patch

Regards

Pavel


Kind Regards,
Peter Smith.
Fujitsu Australia
Attachment

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions
Next
From: "Andrey M. Borodin"
Date:
Subject: Re: recovering from "found xmin ... from before relfrozenxid ..."