"Stored Procedures"- versus "SQL*Forms-only"

From: Martin Berli <berli_at_switch.ch>
Date: 30 Dec 1993 20:25:07 +0100
Message-ID: <2fv9uj$b5_at_scsing.switch.ch>

I'm currently reading Oracle manuals in preparation of the implementation of a database and related applications. I've no practical experiances with Oracle yet.

"Stored Procedures"- versus "SQL*Forms-only"-implementation seems to be an important design decision. I feel that there are many advantages in having procedures as e.g.


stored *in* the database. These procedures could encapsulate complex operations and validity checks on several dependant tables. I also could use these procedures for "first-time-load" of the database, thus having the checks made on each record loaded (and distributed onto the appropriate tables).

SQL*Forms was made before stored procures were available, so the above (without the loading) could be implemented with SQL*Forms only.

Now the question: How much functionality should be implemented in stored procedures, and how much should be left in SQL*Forms? Immediate validation of an entered field value is probably better in SQL*Forms than evaluating an entire form by e.g. one of the mentioned procedures.

I even feel, to be on the secure side, some sort of "double" validation has to be done, in SQL*Forms *and* in a stored procedures...

Has anyone else also thought about these problems, and what are possible solutions? What are your (practical) experiances?

Thanks for any comments.

   Martin Berli

Internet: berli_at_switch.ch  | SWITCH, Swiss Academic and Research Network
Phone   : +41 1 268 1540   | Limmatquai 138
Fax     : +41 1 268 1568   | CH-8001 Zurich
Received on Thu Dec 30 1993 - 20:25:07 CET

Original text of this message