This column has focused on where and how to define code in Oracle Database, but the same rules and logic apply to the Oracle Developer environment. I suggest these guidelines:
• If your program could be useful on both the server side and the client side, move it to the server, because it can be invoked from both sides there.
• If the program is used only in and relevant to client-side modules (it may, for example, manipulate the contents of a field in a form) and you think or know that it will be useful in more than one module, put it into a shared library.
• If your client program is very specific to a current form or report, define it within that module.
No comments:
Post a Comment