| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
| Cc: | doekman(at)icloud(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17550: inet type doesn't accept alternate notations of ipv4 addresses |
| Date: | 2022-07-14 18:02:03 |
| Message-ID: | CAKFQuwbuVC2m-f1L7wOZWhd51Ze_RseJrmY1F_+BX3+wf3Cx3A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jul 14, 2022 at 9:52 AM Francisco Olarte <folarte(at)peoplecall(dot)com>
wrote:
> Doeke:
> On Thu, 14 Jul 2022 at 17:04, PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
> ...
>
> > Anyways, the documentation about the inet-type could say it only accepts
> > normalized forms of addresses.
>
> Asked and answered? I mean, you've already classified this as not a
> bug but a wish, or a feature request.
>
>
I don't see it as unreasonable to claim the lack of documentation regarding
known alternative representations that could be accepted as input is a
bug. The actual report isn't even asking for us to implement acceptance of
those formats, just make it clear when someone gets that error and checks
the docs that the error is valid.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-07-14 18:24:09 | Re: BUG #17550: inet type doesn't accept alternate notations of ipv4 addresses |
| Previous Message | Francisco Olarte | 2022-07-14 16:51:54 | Re: BUG #17550: inet type doesn't accept alternate notations of ipv4 addresses |