2023-05-03 11:06:20 +02:00
== Why is this an issue?
2021-04-28 16:49:39 +02:00
``++SELECT INTO TABLE++`` is much more efficient than ``++SELECT ... ENDSELECT++``. ``++SELECT INTO TABLE++`` needs more memory to hold the result set, but in normal situations, this is not a concern. When memory is a concern, the result set can be divided into smaller sets.
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,abap]
2021-04-28 16:49:39 +02:00
----
SELECT * FROM T006 INTO X006_WA.
...
ENDSELECT.
----
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,abap]
2021-04-28 16:49:39 +02:00
----
SELECT * FROM T006 INTO TABLE X006.
LOOP AT X006 INTO X006_WA.
...
ENDLOOP.
----
2021-04-28 18:08:03 +02:00
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
ifdef::env-github,rspecator-view[]
2021-09-20 15:38:42 +02:00
'''
== Implementation Specification
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== Message
Refactor this select to use "SELECT INTO TABLE int1 + LOOP AT int1".
2021-09-20 15:38:42 +02:00
2021-06-08 15:52:13 +02:00
'''
2021-06-02 20:44:38 +02:00
== Comments And Links
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== on 2 Dec 2014, 14:39:21 Ann Campbell wrote:
\[~freddy.mallet] I'm confused by this description. ``++SELECT INTO TABLE++`` is more efficient but it needs more memory...?
=== on 4 Dec 2014, 09:41:22 Freddy Mallet wrote:
Indeed @Ann:
* In one case, we we're going to consume less memory but the execution time might be really bigger
* In the other case, we start by quickly loading all information in memory to then process it
2021-06-03 09:05:38 +02:00
endif::env-github,rspecator-view[]