Bug 106901

Summary: ds/query-plan/ is broken
Product: [Retired] Red Hat Web Application Framework Reporter: Carsten Clasohm <clasohm>
Component: dev environmentAssignee: ccm-bugs-list
Status: CLOSED WONTFIX QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-07-12 09:02:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 108447    

Description Carsten Clasohm 2003-10-13 08:42:28 UTC 
Description of problem:
When trying to view the Query Execution Plan in Developer Support, you get a
server error.

Version-Release number of selected component (if applicable):
6.0

How reproducible:
always

Steps to Reproduce:
1. Enable Web Developer Support
2. Go to /ccm/ds/ and click on a request with at least one query 
3. Click on the ID of one of the database queries
4. Click on "Query Execution Plan"
    
Actual results:
server error

Expected results:
page displaying the execution plan

Additional info:
This is because of two bugs, or incompatibilities between QueryPlan and the 6.0
persistence code.

1. ConnectionManager.getCurrentThreadConnection() returns null in
QueryPlan.generateQueryPlan().

2. The "queryPlan" query uses "level" as a column name. Persistence transforms
this query into a subquery, generating something like "st_.level as c_7". With
Oracle 9.2, this results in an "ORA-01747: invalid user.table.column,
table.column, or column specification" error, because "level" is a reserved keyword.

The fix can be found in changelist 36898.
Comment 1 Carsten Clasohm 2006-07-12 09:02:24 UTC 
Closing old tickets.