Bug 720762 (rhq-ora-in-clause) - search and fix remaining places in the code where SQL queries containing IN clauses need to be broken into batches of <= 1000 IN clause items to avoid "ORA-01795 maximum number of expressions in a list is 1000" errors from Oracle
Summary: search and fix remaining places in the code where SQL queries containing IN c...
Keywords:
Status: NEW
Alias: rhq-ora-in-clause
Product: RHQ Project
Classification: Other
Component: Core Server
Version: 4.0.1
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 737190 737193 719734 738799 739090
Blocks: rhq-perf jon3 rhq41
TreeView+ depends on / blocked
 
Reported: 2011-07-12 17:14 UTC by Ian Springer
Modified: 2015-02-01 23:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-26 21:30:18 UTC


Attachments (Terms of Use)

Description Ian Springer 2011-07-12 17:14:44 UTC
Joe fixed most of these a while back, but I recently encountered one he missed - Resource import. We should search for any remaining instances that need to be fixed. There are two ways to look for these:

1) grep through the code base looking for them
2) try to do various actions on 1000 or more items via the GUI of the perf environment, which contains 1000s of Resources, looking for ones that bomb

I think there will be many queries with IN clauses in the code base that would never be passed more than 1000 items in a realistic use case, so I think 2) will be an better way to find the important ones that need to be fixed.

Comment 1 Jay Shaughnessy 2013-02-26 21:30:18 UTC
Closing this. This will eventually fall out of perf testing.  Specific instances should be tracked in specific BZs.

Comment 2 Charles Crouch 2013-02-27 22:19:57 UTC
Reopening this, since its a tracker bug. Actually added the keyword this time. 

The specific instances of this problem which jay mentions are listed in the Depends On field of this bug.


Note You need to log in before you can comment on or make changes to this bug.