Re: Oracle & Web Development

Nothing special is required to connect Oracle to a web front end. Your most efficient coding practice will likely be procedures inside of packages as you get all of the advantages of stored procedures along with the ability to have global variables and fewer objects.

Oracle normally, and without doing anything special, caches both SQL code and data with one proviso. That you have set up your instance properly (defining appropriate parameters in the init.ora file) and that you write your SQL using bind variables such that each time Oracle sees a query it recognizes it rather than treating it like a new query that must be handled from scratch.

From the standpoint of adding new fields to tables I have two comments. First the overhead is so minimal you couldn't possibly notice it in a web app. And second, you should not be modifying production tables at a time when it could.

The most important advice I can give you with respect ot Oracle, since you are coming from a SQL Server background is to NOT assume that because Microsoft says its product is similar ... that it is. The differences are staggering. And the more you know Oracle the more you will come to appreciate the differences and their magnitude.

Daniel A. Morgan

Murphy wrote:

> Hello,
>
> Any advice on how to structure Oracle for use in a 3-tier web application? I
> have always used MS SQL Server/COM/ASP and am really intrigued with packages
> and stored functions. I'm thinking that it would be best to use stored procs
> everywhere I can. I would also like to cache some common data in Oracle
> memory so as to keep from having to select the same data for each time the
> ASP is built. I also would like to structure things so that adding new
> fields to tables has a little impact as possible. So could I a package to
> have a level of abstraction between the producer and consumer?
>
> thanks,
> MurF
  Received on Sat Apr 14 2001 - 00:28:58 CDT