Re: Oracle & Web Development

Thanks for the reply. I wanted to make one follow up comment because I wasn't clear in my original post. I wanted the of adding a new field to a table to be as little impact to the over all system as possible. I'm not talking
just in terms of end user but rather the entire system. The fewer modules and code that also has to be changed the better. I am currently supporting a legacy system that was poorly written. They did such things as SELECT * and retrieve the fields by position rather than by name. They also used INSERT VALUES without corresponding field names. And probably worse of all they scattered the database access code through out all 3 tiers. What this means is that any alterations to the table means I have to make changes through out the application. You can bet your bottom dollar that I don't make
these changes in production without first doing it in development, moving through QA and then migrating it into production.

Now that we are moving away from MS SQL Server it will give us a chance to do things right. It wasn't MS SQL Server's fault that the original developer
didn't design the system correctly. The move to Oracle is more political than
technical. I wanted to take advantage of the things that Oracle can offer and
to make sure that I am designing the database as optimally as possible. So getting back to adding a new field I was hoping that by encapsulating every thing in a package I could at least reduce the number of changes that would be made on the database side. I was thinking that the specification should be in the package and the actual implementation in a separate body. Or should it all be combined into a single package? The app is internal but may be opened up to other corporate applications.

thanks,
MurF Received on Sun Apr 15 2001 - 11:00:26 CDT