Pavel Stehule

Thank you for bug report po 2. 9. 2024 v 8:27 odesílatel nkPit ***@***.***> napsal: > Yeah. That fixed the problem. I'm closing the issue. Thank you! > > —...

I have only fragments: Oracle: ``` pINS := 'INSERT INTO OBPDOCUM (LIDENT, ' || mID_NAME || ', ID_CISFOTO, NAZEV_OBPDOCUM, CESTAK, VELIKOST_DOCUM, POZNAMKA, PLATNOST_OD' || ', ID_ASPRAVCE, ID_APROVOZNA, ID_SKUP_CISEL, DRUHAK, CVZNIKRADK,...

pá 17. 1. 2025 v 15:47 odesílatel Gilles Darold ***@***.***> napsal: > ok, I have never met this syntax so conversion it is not implemented. I > will try to...

po 21. 10. 2024 v 4:12 odesílatel Gilles Darold ***@***.***> napsal: > Hi Pavel, > > Normally you just have to set PG_VERSION to the version of the PostgreSQL >...

po 21. 10. 2024 v 8:57 odesílatel Gilles Darold ***@***.***> napsal: > Commit 0a22650 > > might support overriding of the PG_VERSION automatic adjustment of these > PG_SUPPORT_* variables. >...

My customer did some tests and, unfortunately, reported few issues: 1. Although the procedure is converted to function, it is called by `CALL` statement instead `SELECT` 2. Transformed function use...

I have check report from my customer. He found still one issue. When procedure has more OUT arguments, then migration is ok, but when procedure has just one OUT argument,...

Unfortunately, it is not fixed (on procedures). It was not when Oracle's procedures are converted to postgres functions.