On 31/05/2021 13:34, Dmitry Yemanov wrote: > 31.05.2021 17:49, Dimitry Sibiryakov пишет: >> 31.05.2021 16:19, Alex Peshkoff via Firebird-devel wrote: >>> Dimitry, can you provide standard syntax for others to compare? >> >> https://ronsavage.github.io/SQL/sql-2003-2.bnf.html#call%20statement > > As far as I see, it's the same as EXECUTE PROCEDURE without outputs. But > we already have non-standard RETURNING added to standard I/U/D > statements, so what's the difference? > > Even if the majority objects this idea, we can still utilize CALL in the > standard way, i.e. use it when calling procedures that don't return > outputs (or we are willing to ignore them). >
I do not known exactly how standard SQL procedures works, but given that majority of engines supports IN/OUT parameters together, CALL could also return results. Our procedures IMO is better separating IN/OUT, but requires adaptation to CALL to return values. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
