Comments on: Dependency Injection in PL/SQL – Remove Hard Coded Dependencies from your code

By: Mehmet Kirazoglu

Mehmet Kirazoglu — Wed, 21 Sep 2011 13:15:52 +0000

I agree with Mike Friedman. What can be the point of initializing every package and load them to memory on every logon?

By: spaxx

spaxx — Sun, 26 Mar 2006 12:20:55 +0000

I entirely agree with karl. I too was wondering if design patterns exist in pl-sql just
as they do in Java/J2ee. This example is proof that pl-sql is well on its way to
having its own certified design patterns. I hope that this can be advanced to include many production-environment tested scenarios.

By: Mike Friedman

Mike Friedman — Wed, 08 Mar 2006 01:18:10 +0000

What is the impact of this approach on performance in connectionless environments like the web?

Seems you could spend an awful lot of time initializing packages that will not need to be initialized in that particular session.

By: andrew

andrew — Tue, 07 Mar 2006 21:57:07 +0000

Surely the initialization section of each package could use execute immediate to get around the compile dependency?

Another disadvantage of the LOGON trigger is that you can’t use DBMS_SESSION.reset_package in your code to cleanup state (it’s useful in a connection-pooling environment at the start or end a logical session). The one big advantage of hardoding values in APP_CONSTANTS is that all values needed by the other packages are garanteed to exist in APP_CONSTANTS and be set to something – else the dependant packages won’t compile. Deploying new code to a production environment without creating the new configuration rows is a sure way to get egg on your face…

Great article though!

By: karl

karl — Tue, 07 Mar 2006 20:41:34 +0000

Hi,
these kind of design oriented articles for PL/SQL are very rare! So i am very delighted to see an article focused on PL/SQL Aspects – looking not to close to the langauge features but show a wider concept of design and implementation.

Great!
Karl