2023-05-03 11:06:20 +02:00
== Why is this an issue?
2021-04-28 16:49:39 +02:00
Oracle supports at most 1000 items in a SQL query's ``++IN++`` clause. When more items are given, the exception ``++ORA-01795 maximum number of expressions in a list is 1000++`` is raised. Thus, ``++IN++`` clauses are not as scalable as joins.
2021-04-28 18:08:03 +02:00
2023-05-03 11:06:20 +02:00
=== Noncompliant code example
2021-04-28 16:49:39 +02:00
2022-02-04 17:28:24 +01:00
[source,sql]
2021-04-28 16:49:39 +02:00
----
BEGIN
SELECT *
INTO result
FROM my_table
WHERE col1 IN (1, 2, 3, ..., 1001); -- Noncompliant - raises ORA-01795
END;
/
----
2021-04-28 18:08:03 +02:00
2023-05-03 11:06:20 +02:00
=== Compliant solution
2021-04-28 16:49:39 +02:00
2022-02-04 17:28:24 +01:00
[source,sql]
2021-04-28 16:49:39 +02:00
----
BEGIN
SELECT my_table.*
INTO result
FROM my_table
JOIN new_in_table
WHERE my_table.col1 = new_in_table.value; -- Compliant
END;
/
----
2021-04-28 18:08:03 +02:00
2021-09-20 15:38:42 +02:00
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== Message
Refactor this query to use a "JOIN" instead.
=== Parameters
.maximumNumberOfItems
****
----
50
----
Maximum number of items allowed
****
2021-09-20 15:38:42 +02:00
endif::env-github,rspecator-view[]