Debian Codegraph @

mysql-test/suite/x/r/message_large_payload.result

raw
1 CREATE SCHEMA xtest;
2 CREATE TABLE xtest.xtable (value TEXT);
3 INSERT INTO xtest.xtable(value) VALUES("");
4 SET GLOBAL mysqlx_max_allowed_packet = 2097152;
5
6
7 ## I. Verify that sending an X Protocol message that generates
8 ## SQL larger than a certain limit (SQL > 1MB) doesn't
9 ## return ER_QUERY_INTERRUPTED.
10 #
11 # 1. Send StmtExecute with 1MB encoded literal.
12 # 2. Send CRUD-find with 1MB encoded literal.
13 # 3. Send CRUD-delete with 1MB encoded literal.
14 # 4. Send CRUD-insert with 1MB encoded literal.
15 # 5. Send CRUD-update with 1MB encoded literal.
16 # 6. Send CRUD-CreateView with 1MB encoded literal.
17 # 7. Send Mysqlx.Prepare.Prepare with 1MB encoded literal.
18 # 8. Send Mysqlx.Cursor.Open with 1MB encoded literal.
19
20
21 #
22 # I.1
23 ## Send large message
24 result
25 %LARGE_TEXT%
26 0 rows affected
27
28 #
29 # I.2
30 result
31 %LARGE_TEXT%
32 command ok
33
34 #
35 # I.3
36
37 0 rows affected
38
39 #
40 # I.4
41 Got expected error: Data too long for column 'value' at row 1 (code 1406)
42
43 #
44 # I.5
45 Got expected error: Data too long for column 'value' at row 1 (code 1406)
46
47 #
48 # I.6
49 RUN recvok
50
51 #
52 # I.7
53 RUN recvok
54
55 #
56 # I.8
57 RUN recvok
58 result
59 command ok
60 Mysqlx.Ok {
61 msg: "bye!"
62 }
63 ok
64 SET GLOBAL mysqlx_max_allowed_packet = DEFAULT;