Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp

2025-11-26 Thread Amit Langote
Hi, On Wed, Nov 26, 2025 at 8:43 PM Michael Paquier wrote: > On Wed, Nov 26, 2025 at 03:09:25PM +0530, Amul Sul wrote: > > This continues the previous refactoring commit [1] where we adopted > > soft error reporting for some numeric functions. This patch applies > > the same pattern to the date/t

Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp

2025-11-26 Thread Michael Paquier
On Wed, Nov 26, 2025 at 03:09:25PM +0530, Amul Sul wrote: > This continues the previous refactoring commit [1] where we adopted > soft error reporting for some numeric functions. This patch applies > the same pattern to the date/timestamp function. The change ensures > consistency by utilizing the

Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp

2025-11-26 Thread Amul Sul
Hi, The attached patch proposes to use soft error reporting infrastructure for the date/timestamp conversion function, which currently depends on integer variables to control error throwing. This continues the previous refactoring commit [1] where we adopted soft error reporting for some numeric