Progress
DataServer
for ORACLE Guide
Programming Considerations
The Progress ADE used in conjunction with the DataServer allows you to develop applications that transparently access data from multiple sources. The DataServer for ORACLE achieves database transparency for applications running against Progress and ORACLE, but some of the ways it accomplishes this might affect how you develop applications. This chapter discusses the differences between Progress and ORACLE that you have to consider when you plan your applications and design your databases. In addition, your applications might have to accommodate the strategies that the DataServer uses to resolve these differences.
This chapter discusses equivalencies and differences between ORACLE and Progress in the following areas:
- Database design issues, including database objects, naming conventions, character sets, indexes, views, database triggers, and sequence generators
- Application development issues including, data types, arrays, record creation, record locking, transactions, error handling, and cursor repositioning
- Progress 4GL issues, including the ROWID function, the FIND statement, and the COMPILE statement
Mapping Progress to ORACLE
The material in this chapter is also of interest to users who plan to migrate a Progress database to ORACLE. However, this migration raises several additional issues that are discussed in the "The Progress-to-ORACLE Utility" section in The DataServer Tutorial."
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |