0876-0876
Page 876
- Minimize the number of queries. If a POST-QUERY trigger is called for every row returned by the initial query, create a view that contains all the information in the first query.
- Combine unrelated queries if possible. Several queries that all return one row using a unique index can be combined into a single query. This saves round-trips over the network.
- Use database triggers and procedures where possible. These constructs ensure that all maintenance to the data uses the same business rules. Additionally, communications to the database are minimized.
- Finally, before rolling out to production, stress test the application with a large volume of data with many users. This testing shakes out bottlenecks and indicates where you might need to revise locking strategies.
Summary
The material presented in this chapter defines the primary building blocks for creating Oracle Forms applications that access data in an Oracle database. Items are built into form blocks, which appear on a canvas in defined windows . Triggers and program units combine to provide a robust development system that can be customized to the specific needs of the end users. Properties, lists of values, alerts, and the various graphical objects further enhance your ability to construct useful and powerful database applications.
Unfortunately, because of the limitations of defining the entire tool in a single chapter, I did not explain many of the topics in as much detail as is needed to make you an expert developer. What I hope to provide you is a set of tools and the basic knowledge to use them. You can think of yourself now as the equivalent of an apprentice carpenter fresh out of trade school. Only with experience using the tools can the apprentice hone his skills until he can be considered a master craftsman. Likewise, the only way to learn how to use a tool set as powerful as Oracle Forms is to use the tool and try new techniques until you, too, are an expert.
EAN: 2147483647
Pages: 391