File: order_by_zerolength-4285.test

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 772,520 kB
  • sloc: ansic: 2,414,714; cpp: 1,791,394; asm: 381,336; perl: 62,905; sh: 49,647; pascal: 40,897; java: 39,363; python: 20,791; yacc: 20,432; sql: 17,907; xml: 12,344; ruby: 8,544; cs: 6,542; makefile: 6,145; ada: 1,879; lex: 1,193; javascript: 996; objc: 80; tcl: 73; awk: 46; php: 22
file content (29 lines) | stat: -rw-r--r-- 948 bytes parent folder | download | duplicates (6) 
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
 
#
# MDEV-4285 Server crashes in ptr_compare on NOW and CAST in ORDER BY
#
create table t1 (pk int primary key);
insert into t1 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10);

# In strict mode the query produces result in a different order
# (not ordered implicitly by PK and indeterministic), so we force sorting.
# However, sorting also affects warnings, so we'll check them separately.
--disable_warnings
--sorted_result
select * from t1 order by now(), cast(pk as char(0));
--enable_warnings
show warnings;
drop table t1;

--echo #
--echo # MDEV-17020: Assertion `length > 0' failed in ptr_compare upon ORDER BY with bad conversion
--echo #

set @save_sql_mode= @@sql_mode;
SET @@sql_mode= '';
CREATE TABLE t1 (pk INT PRIMARY KEY);
INSERT INTO t1 VALUES (1),(2);
explain
SELECT * FROM t1 ORDER BY 'foo', CONVERT(pk, CHAR(0)) LIMIT 2;
SELECT * FROM t1 ORDER BY 'foo', Cast(pk as CHAR(0)) LIMIT 2;
set @@sql_mode= @save_sql_mode;
drop table t1;