Skip to main content

Hi @all,

we are now migrating our application from Oracle to Postgres DB. The former procedures in the ORA packages are converted into PGS functions returning void.

The literal function and parameter names are switched into lowercase in the SSP-signatures. Those functions which have only in-parameters delivers an ODBC error for an invalid parameter type. After changing the parameter from in to in/out the call works. But IMHO this can't be the right solution. When we use an entity field as parameter the call flags the field as modified and the Lock-trigger is fired.
Is this a bug or is there any other solution avialable?

TiA!

Kind regards from Germany

Reinhard Lechner

 (UnifAce developer since 1994)



------------------------------
Reinhard Lechner
CAL Consult Gmbh
------------------------------

Hi @all,

we are now migrating our application from Oracle to Postgres DB. The former procedures in the ORA packages are converted into PGS functions returning void.

The literal function and parameter names are switched into lowercase in the SSP-signatures. Those functions which have only in-parameters delivers an ODBC error for an invalid parameter type. After changing the parameter from in to in/out the call works. But IMHO this can't be the right solution. When we use an entity field as parameter the call flags the field as modified and the Lock-trigger is fired.
Is this a bug or is there any other solution avialable?

TiA!

Kind regards from Germany

Reinhard Lechner

 (UnifAce developer since 1994)



------------------------------
Reinhard Lechner
CAL Consult Gmbh
------------------------------

Hi Reinhard,

For basic parameter types, you are able to use IN, OUIT and INOUT, but for entity type parameters it must be IN or INOUT. This is the same across the supported databases.

There is a note explaining it in the documentation here: 

Entity Parameters
When defining an operation with an entity parameter in a Uniface signature, you can define an entity parameter only as OUT or INOUT, but when creating the corresponding stored procedure in SQL Server, you must define the parameter as an OUTPUT string.

Mike



------------------------------
Michael Taylor
Rocket Internal - All Brands
------------------------------
Terms & ConditionsAccessibility statement