Uniface-generated stored procedures
Author: firstname.lastname@example.org (tandron)
Under what circumstances are Uniface-generated stored procedure necessary or useful ? I have experimented running an 9.3.02 application with ,and without, the proc parameter in the server application asn file. It seems to be running just fine (if not faster) without the proc parm and the usage of the stored procedures.
When proc is used, Uniface will derive the Sn (entityname_S1, ...S2, etc) procedure to be used for retrieving data based on the profile used by the form. The Sn procedure will be using the Index n. If there is a mismatch between the Index n and the procedure n (procedure is defined with input fields different from the fields on which the index n is defined), then retrieve will fail. This mismatch will definitely happen when new indexes are added to the entity in the model (not always when constraints are defined). The solution is to drop the indexes and and regenerate the stored proc but this is a lot of work for what apparently is zero benefit.
Does anyone have a better understanding of how this works? is this a relic from past Uniface versions? What has been your experience with Uniface-gnerated stored procs?