OCIError: ORA-01795: maximum number of expressions in a list is 1000
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the Oracle error through the rom-repository combine and aggregate entry points, then inspect the subselect SQL they generate and compare it with the suggested wrap join approach. Done means identifying and documenting a supported workaround or a defined change that avoids Oracle's 1000-expression limit.
Written by the indexing model from the issue text.
Description
We get this error often when we use combine or aggregate in a rom-repository:
OCIError: ORA-01795: maximum number of expressions in a list is 1000
I believe this is because the above methods use subselects under the hood. Another option would be to use joins (eg. with wrap) but this is not feasible in our case.
Would it be possible to override this limitation of 1000 items in a list? Alternatively, is there a workaround you could suggest for this perhaps?
Your help would be much appreciated.
- Dominant language
- Ruby
- Stars
- 220
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rom-rb/rom-sql
-
bug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
bug help wanted
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
bug help wanted
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
bug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
bug help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) OpenBug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TheOdinProject/curriculum#31402 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100