File: charset_client_win_utf8mb4.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 (28 lines) | stat: -rw-r--r-- 915 bytes parent folder | download 
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
 
--source include/windows.inc
--source include/check_utf8_cli.inc

if(!`select $MTR_PARALLEL = 1`)
{
  skip race condition with parallel tests;
}

--exec $MYSQL --default-character-set=auto -e "select @@character_set_client"

# Test that a user with old, non-UTF8 password can still connect
# by setting setting non-auto --default-character-set
# This is important for backward compatibility

# Emulate creating password in an interactive client session, with older clients
# which communicates with the server using with something like cp850

exec chcp 850 > NUL && echo CREATE USER 'u' IDENTIFIED by 'ü' | $MYSQL --default-character-set=cp850;


# Can't connect with UTF8
--error 1
exec $MYSQL --default-character-set=auto --user=u --password=ü  -e "select 1" 2>&1;

# Can connect with tweaked --default-character-set
exec $MYSQL --default-character-set=cp850 --user=u --password=ü -e "select 2";
DROP user u;