po 12. 12. 2022 v 14:16 odesílatel Мельников Игорь
napsal:
> I know, know.
> But ora2pg NOT convert source code in application tier anonymouse block
> and dynamic SQL in server side pl/sql.
> This part of application need to be rewrite manually.
>
> "no_data_found" for the plpgsql.extra_errors
I know, know.
But ora2pg NOT convert source code in application tier anonymouse block and
dynamic SQL in server side pl/sql.
This part of application need to be rewrite manually.
"no_data_found" for the plpgsql.extra_errors and plpgsql.extra_warnings will
be reduce this part of work.
Also,
Hi
po 12. 12. 2022 v 13:37 odesílatel Мельников Игорь
napsal:
> Hi!
>
> This new feature will be in demand for customers who migrate their
> largeapplications (having millions of lines of PL/SQL code) from Oracle to
> PostreSQL.
> It will reduce the amount of work on rewriting the code will
Hi!
This new feature will be in demand for customers who migrate their
largeapplications (having millions of lines of PL/SQL code) from Oracle to
PostreSQL.
It will reduce the amount of work on rewriting the code will provide an
opportunity to reduce budgets for the migration project.
Yes,
On 09.12.2022 09:46, Pavel Stehule wrote:
I don't like the idea about possible replacement of INTO STRICT by INTO
+ extra warnings.
Handling exceptions is significantly more expensive than in Oracle, and
using INTO without STRICT with the next test IF NOT FOUND THEN can save
one safepoint
čt 8. 12. 2022 v 12:29 odesílatel Sergey Shinderuk <
s.shinde...@postgrespro.ru> napsal:
> Hello,
>
> I propose to add a new value "no_data_found" for the
> plpgsql.extra_errors and plpgsql.extra_warnings parameters [1].
>
> With plpgsql.extra_errors=no_data_found SELECT INTO raises no_data_found
Hello,
I propose to add a new value "no_data_found" for the
plpgsql.extra_errors and plpgsql.extra_warnings parameters [1].
With plpgsql.extra_errors=no_data_found SELECT INTO raises no_data_found
exception when the result set is empty. With
plpgsql.extra_errors=too_many_rows,no_data_found
