Re: [PATCH] Add roman support for to_number function

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Hunaid Sohail <hunaidpgml(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [PATCH] Add roman support for to_number function
Date: 2024-12-08 00:36:38
Message-ID: 4b02c674-bae5-40ab-96cc-635b661df6d4@vondra.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 10/30/24 08:07, Hunaid Sohail wrote:
> Hi,
>
> I have attached a rebased patch if someone wants to review in the next
> CF. No changes as compared to v4.
>
> Regards,
> Hunaid Sohail
>

Thanks for a nice patch. I did a quick review today, seems almost there,
I only have a couple minor comments:

1) Template Patterns for Numeric Formatting

Why the wording change? "input between 1 and 3999" sounds fine to me.

2) The docs say "standard numbers" but I'm not sure what that is? We
don't use that term anywhere else, I think. Same for "standard roman
numeral".

3) A couple comments need a bit of formatting. Multi-line comments
should start with an empty line, some lines are a bit too long.

4) I was wondering if the regression tests check all interesting cases,
and it seems none of the tests hit these two cases:

if (vCount > 1 || lCount > 1 || dCount > 1)
return -1;

and

if (!IS_VALID_SUB_COMB(currChar, nextChar))
return -1;

I haven't tried constructing tests to hit those cases, though.

Seems ready to go otherwise.

regards

--
Tomas Vondra

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2024-12-08 02:23:42 Re: Do not scan index in right table if condition for left join evaluates to false using columns in left table
Previous Message Tomas Vondra 2024-12-07 23:57:32 Re: CREATE SUBSCRIPTION - add missing test case