- 新しい順
- 投票が多い順
- コメントが多い順
Hello,
In addition to the above, please let me inform you that XML parsing functionality does not require translation to PL/pgSQL. Many operations can be solved with the combination of using PG XPATH and UNNEST functions within T-SQL. This way you can avoid the nested transaction problem.
Using PG native XPATH() - https://www.postgresql.org/docs/15/functions-xml.html#FUNCTIONS-XML-PROCESSING
With PG native UNNEST() - https://www.postgresql.org/docs/15/functions-array.html
I would recommend you to please replicate on your instance and let us know if you face any issues over support case.
Thank you.
Short answer: no. One cannot combine T-SQL and PostgreSQL transaction semantics in the same transaction.
A common approach is to invoke a function in pg/PLsql from T-SQL, and implement the pg/PLsql function without transaction control commands.
関連するコンテンツ
- AWS公式更新しました 2年前
Thanks, Lakshmi.
Even if the XML-related functions you mentioned allow to workaround the particular use case of using TSQL XML functions, there are still a lot of other Babelfish incompatibilities listed in the Babel Compass report that require a workaround through the usage of PL/pgSQL scripts; thus, the ability to have a nested transaction is still relevant.