Categories
Editor for Logical Queries

Description
Create a new editor to enter and execute Logical Quries
Use Case and Business Need
At present report developers uses Physical SQLs to create BI Publisher report instead of using Analysis due to many reasons such as:
- Many developers are from EBS background, and have worked with XML Publisher in past. They are more comfortable with creating BI Publisher report over using OTBI Subject Areas due to lack of experience.
- Experienced developers like to write code than designing it.
- Writing code is more flexible than designing it.
However, using OTBI Subject Areas to create Analysis, or use such analysis to further create BI Publisher report has many merits such as:
- No need to worry about join conditions.
- Number of facts and dimensions to remember while working with Logical Queries are far less than number of tables/views while working with Physical Queries.
- Chances of human error are high while working with Physical Queries
- Physical Queries may or may not perform as good as analysis built on top of dashboard etc.
Idea is to offer developers a feature-rich SQL editor for entering and executing Logical Queries. Developers will have many incentives in terms of time and efforts required to build a report, when using this new editor over writing physical queries such as:
- Presentation tables hides all complexities such as underlying tables/views and joins.
- Presentation tables are far less in number as compared to physical tables or views they cover.
- No need to remember join.
- Query built will use proven security and performance standards
- Ability to write and execute queries.
It will also prove beneficial for Oracle in the long run since reports built using Logical Queries will have lesser bug, or performance or security related issue. Also, any such issue identified, once fixed, can be deployed for other customers as well.
Original Idea Number: 8a4c54e6c2
Comments
-
I assume that this would remove visibility of data to developers who have not been granted the access. For example, a financial developer should not be able to query payroll data like they can today.
0