|
Как применить строковую функцию только к части выборки?
#39627889
Ссылка:
Ссылка на сообщение:
Ссылка с названием темы:
Ссылка на профиль пользователя:
|
|
|
|
Не знаю, это предположение и может быть причина в другом.
Вот DDL основной таблицы:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.
99.
100.
101.
102.
103.
104.
105.
106.
107.
108.
109.
110.
111.
112.
113.
114.
115.
116.
117.
118.
119.
120.
121.
122.
123.
124.
125.
126.
127.
128.
129.
130.
131.
132.
133.
134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.
146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.
158.
159.
160.
161.
162.
163.
164.
165.
166.
167.
168.
CREATE TABLE BM_ACTION_LOG
(
ACTION_LOG_ID NUMBER NOT NULL,
ACTION_ID NUMBER NOT NULL,
SUB_ACTION_ID NUMBER,
STAFF_ID NUMBER,
SCRIPT_NAME VARCHAR2(255 BYTE) NOT NULL,
CUSTOMER_ID NUMBER,
ACCOUNT_ID NUMBER,
SERVICE_ID NUMBER,
GROUP_ID NUMBER,
DOMAIN_ID NUMBER,
TARGET_ID NUMBER,
OLD_VALUE VARCHAR2(255 BYTE),
NEW_VALUE VARCHAR2(255 BYTE),
REMOTE_ADDR VARCHAR2(255 BYTE),
STAFF_COMMENT VARCHAR2(255 BYTE),
MOMENT DATE NOT NULL
)
TABLESPACE BM_DATA
PCTUSED 0
PCTFREE 10
INITRANS 1
MAXTRANS 255
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;
CREATE UNIQUE INDEX ACTION_LOG_PK ON BM_ACTION_LOG
(ACTION_LOG_ID)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
REVERSE;
CREATE INDEX BM_ACTLOG_ACCOUNT_ID_IDX ON BM_ACTION_LOG
(ACCOUNT_ID)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
COMPRESS 1;
CREATE INDEX BM_ACTLOG_ACTION_ID_IDX ON BM_ACTION_LOG
(ACTION_ID)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
COMPRESS 1;
CREATE INDEX BM_ACTLOG_CUSTOMER_ID_IDX ON BM_ACTION_LOG
(CUSTOMER_ID)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
COMPRESS 1;
CREATE INDEX BM_ACTLOG_DOMAIN_ID_IDX ON BM_ACTION_LOG
(DOMAIN_ID)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
COMPRESS 1;
CREATE INDEX BM_ACTLOG_GROUP_ID_IDX ON BM_ACTION_LOG
(GROUP_ID)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
COMPRESS 1;
CREATE INDEX BM_ACTLOG_MOMENT_IDX ON BM_ACTION_LOG
(MOMENT)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
COMPRESS 1;
CREATE INDEX BM_ACTLOG_SERVICE_ID_IDX ON BM_ACTION_LOG
(SERVICE_ID)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
COMPRESS 1;
CREATE INDEX BM_ACTLOG_STAFF_ID_IDX ON BM_ACTION_LOG
(STAFF_ID)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
COMPRESS 1;
CREATE INDEX BM_ACTLOG_SUB_ACTION_ID_IDX ON BM_ACTION_LOG
(SUB_ACTION_ID)
LOGGING
TABLESPACE BM_INDEX
PCTFREE 10
INITRANS 2
MAXTRANS 255
NOPARALLEL
COMPRESS 1;
CREATE OR REPLACE TRIGGER auto_action_log
BEFORE INSERT OR UPDATE OF action_log_id ON BM_ACTION_LOG FOR EACH ROW
BEGIN
IF((:new.action_log_id IS NULL) OR (:new.action_log_id = 0))
THEN
SELECT action_log_seq.NEXTVAL
INTO :new.action_log_id
FROM DUAL;
SELECT SYSDATE
INTO :new.moment
FROM DUAL;
END IF;
END;
/
CREATE OR REPLACE TRIGGER ts_action_log
BEFORE INSERT OR UPDATE ON BM_ACTION_LOG FOR EACH ROW
BEGIN
IF(:new.moment IS NULL)
THEN
SELECT SYSDATE
INTO :new.moment
FROM DUAL;
END IF;
END;
/
Запрос в целом базируется на таком:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
SELECT
bm_action.action_desc bm_action_action_desc,
bm_sub_action.description bm_sub_action_description,
bm_staff.login bm_staff_login,
bm_staff.first_name bm_staff_first_name,
bm_staff.middle_name bm_staff_middle_name,
bm_staff.last_name bm_staff_last_name,
services.service_id services_service_id,
services.login services_login,
accounts.account_id accounts_account_id,
customers.customer_id customers_customer_id,
bm_action_log.action_id bm_action_log_type,
bm_action_log.staff_comment bm_action_log_staff_comment,
bm_action_log.script_name bm_action_log_script_name,
bm_action_log.target_id bm_action_log_target_id,
bm_action_log.old_value bm_action_log_old_value,
bm_action_log.new_value bm_action_log_new_value,
bm_action_log.remote_addr bm_action_log_remote_addr,
bm_action_log.moment bm_action_log_moment
FROM
bm_action_log
, bm_action
, bm_sub_action
, bm_staff
, services
, accounts
, customers
WHERE
bm_action_log.action_id = bm_action.action_id (+) AND
bm_action_log.sub_action_id = bm_sub_action.sub_action_id (+) AND
bm_action_log.staff_id = bm_staff.staff_id (+) AND
bm_action_log.service_id = services.service_id (+) AND
bm_action_log.account_id = accounts.account_id (+) AND
bm_action_log.customer_id = customers.customer_id (+) AND
bm_action_log.service_id = $service_id AND
bm_action_log.customer_id = $customer_id AND
bm_action_log.account_id = $account_id AND
bm_action_log.staff_id IS NULL AND
bm_staff.login like $staff_login AND
bm_action_log.moment > $quote_start AND
bm_action_log.moment < $quote_stop AND
bm_action_log.domain_id = $domain_id AND
bm_action_log.action_id IN ( $actions )
ORDER BY bm_action_log.moment DESC
(строки, где указаны переменные с символом доллара, формируются динамически, в зависимости от выбранных условий)
Но в серверном коде он как-то обрабатывается дополнительно, потому что там есть листание по страницам. Где это делается в коде я пока не нашел, скорее всего это какой-то общий механизм, вынесенный в отдельную библиотеку.
Вот пример запроса с конкретными параметрами:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
SELECT
bm_action.action_desc bm_action_action_desc,
bm_sub_action.description bm_sub_action_description,
bm_staff.login bm_staff_login,
bm_staff.first_name bm_staff_first_name,
bm_staff.middle_name bm_staff_middle_name,
bm_staff.last_name bm_staff_last_name,
services.service_id services_service_id,
services.login services_login,
accounts.account_id accounts_account_id,
customers.customer_id customers_customer_id,
bm_action_log.action_id bm_action_log_type,
bm_action_log.staff_comment bm_action_log_staff_comment,
bm_action_log.script_name bm_action_log_script_name,
bm_action_log.target_id bm_action_log_target_id,
bm_action_log.old_value bm_action_log_old_value,
bm_action_log.new_value bm_action_log_new_value,
bm_action_log.remote_addr bm_action_log_remote_addr,
bm_action_log.moment bm_action_log_moment
FROM
bm_action_log
, bm_action
, bm_sub_action
, bm_staff
, services
, accounts
, customers
WHERE
bm_action_log.action_id = bm_action.action_id (+) AND
bm_action_log.sub_action_id = bm_sub_action.sub_action_id (+) AND
bm_action_log.staff_id = bm_staff.staff_id (+) AND
bm_action_log.service_id = services.service_id (+) AND
bm_action_log.account_id = accounts.account_id (+) AND
bm_action_log.customer_id = customers.customer_id (+) AND
--bm_action_log.service_id = $service_id AND
--bm_action_log.customer_id = 90007 AND
--bm_action_log.account_id = $account_id AND
--bm_action_log.staff_id IS NULL AND
--bm_staff.login like $staff_login AND
bm_action_log.moment > DATE'2018-01-01' AND
bm_action_log.moment < DATE'2018-01-10' AND
bm_action_log.domain_id = 1 AND
bm_action_log.action_id IN ( 306 )
ORDER BY bm_action_log.moment DESC
В веб-интерфейсе информационной системы и в TOAD запрос с такими параметрами выполняется менее секунды.
Если поле bm_action_log_staff_comment я формирую в зависимости от bm_action_log.action_id и определенного параметра, зависящего от текущего пользователя, то в информационной системе этот запрос выполняется очень долго. В TOAD я его повторить пока не могу. |
|
|
