PL/Java is a free add-on module that brings Java™ Stored Procedures, Triggers, Functions, Aggregates, Operators, Types, etc., to the PostgreSQL™ backend.
When generating a function declaration for a function with exactly one OUT parameter, the declaration must have the scalar form where RETURNS identifies the single parameter's own type instead of RECORD.
Added more checks on co-appearance of type= and out= and a way to use @SQLType to disambiguate in cases where the method "shape" would fit a composite-returning method or an ordinary method with a row-typed trailing input parameter.
In cases where PL/Java has relied on an assumption in generating a function's declaration (some of the assumptions have long standing in PL/Java history), it still proceeds silently at compile time, but generates a comment into the deployment descriptor identifying the assumption and how to annotate the method if a different interpretation is intended.
When generating a function declaration for a function with exactly one
OUTparameter, the declaration must have the scalar form whereRETURNSidentifies the single parameter's own type instead ofRECORD.Discussion: https://www.postgresql.org/message-id/619BBE78.7040009%40anastigmatix.net
Added more checks on co-appearance of
type=andout=and a way to use@SQLTypeto disambiguate in cases where the method "shape" would fit a composite-returning method or an ordinary method with a row-typed trailing input parameter.In cases where PL/Java has relied on an assumption in generating a function's declaration (some of the assumptions have long standing in PL/Java history), it still proceeds silently at compile time, but generates a comment into the deployment descriptor identifying the assumption and how to annotate the method if a different interpretation is intended.
Addresses #386.