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

From Pavel Stehule
Subject Re: proposal - function string_to_table
Date
Msg-id CAFj8pRCddAp8_hzdQjRSb4f+GkM8V2NSJXLCKigx-3SBcqr22g@mail.gmail.com
Whole thread Raw
In response to Re: proposal - function string_to_table  ("movead.li@highgo.ca" <movead.li@highgo.ca>)
Responses Re: proposal - function string_to_table
List pgsql-hackers
Hi

čt 4. 6. 2020 v 11:49 odesílatel movead.li@highgo.ca <movead.li@highgo.ca> napsal:
+{ oid => '2228', descr => 'split delimited text',
+  proname => 'string_to_table', prorows => '1000', proretset => 't',
+  prorettype => 'text', proargtypes => 'text text',
+  prosrc => 'text_to_table' },
+{ oid => '2282', descr => 'split delimited text with null string',
+  proname => 'string_to_table', prorows => '1000', proretset => 't',
+  prorettype => 'text', proargtypes => 'text text text',
+  prosrc => 'text_to_table_null' },

I go through the patch, and everything looks good to me. But I do not know
why it needs a 'text_to_table_null()', it's ok to put a 'text_to_table' there, I think.

It is a convention in Postgres - every SQL unique signature has its own unique internal C function.

I am sending a refreshed patch.

Regards

Pavel






Regards,
Highgo Software (Canada/China/Pakistan)
URL : www.highgo.ca
EMAIL: mailto:movead(dot)li(at)highgo(dot)ca
Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Transactions involving multiple postgres foreign servers, take 2
Next
From: Pavel Stehule
Date:
Subject: minor doc fix - garbage in example of result of unnest