There is a great debate among programmers as to what should you use to code customizations—SQR or Application Engine? Many programmers are familiar with SQR, so it is easy to find coders. Application Engine is relatively new, and there is less familiarity with the product.
Some programmers just use the PeopleCode part of Application Engine because they do not understand the set-based SQL language. Many of the delivered reports are written in SQR.
- Application Engine has knowledge of all the objects in the application, whereas SQR is a stand-alone language.
- Application Engine can utilize any code that is stored in the database, whereas unless it is written as an SQC, SQR has to re-add the code each time.
- Currently, Oracle does not have a good batch processing tool. Since Application Engine is a set-based tool, it pushes processing to the database, and this fits well with Oracle products.
- It does not look as if Oracle is planning to invest in SQR. Even at the conferences the emphasis is to use Application Engine as the primary batch tool.
- Recommendation is to do new customizations in Application Engine, so that it will be easier to move forward..
- As time permits, convert SQR to XML Publisher or Application Engine, depending on the Functions
