Re: Proposal to add a new URL data type.
От | Daniel Gustafsson |
---|---|
Тема | Re: Proposal to add a new URL data type. |
Дата | |
Msg-id | 5CDF62D7-64B5-469C-B446-0D11464F6767@yesql.se обсуждение исходный текст |
Ответ на | Re: Proposal to add a new URL data type. (Alexander Borisov <lex.borisov@gmail.com>) |
Ответы |
Re: Proposal to add a new URL data type.
Re: Proposal to add a new URL data type. |
Список | pgsql-hackers |
> On 6 Dec 2024, at 13:59, Alexander Borisov <lex.borisov@gmail.com> wrote: > As I've written before, there is a difference between parsing URLs > according to the RFC 3986 specification and WHATWG URLs. This is > especially true for host. Here are a couple more examples. As someone who wears another open-source hat which is heavily involved in parsing URLs I cannot stress enough how much I think postgres should avoid this. The example url http://http://http://@http://http://?http://#http:// is a valid url, but is rejected by a number of implementations and parsed differently by most that accept it. A URL datatype is a *good idea* but one which I personally believe is best handled as an external extension. -- Daniel Gustafsson
В списке pgsql-hackers по дате отправления: