Details
- 
    
Bug
 - 
    Status: Closed (View Workflow)
 - 
    
Major
 - 
    Resolution: Not a Bug
 - 
    10.0(EOL), 10.1(EOL), 10.2(EOL)
 - 
    None
 
Description
Propably the fix of MDEV-11079 introduced another regression:
The attached testcase yields to the following error on mariadb 10.0.31:
					@@ -5,5 +5,5 @@
			 | 
		
					 x      HEX(y)
			 | 
		
					 ÄÖÜ    000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F202122232425262728292A2B2C2D2E2F303132333435363738393A3B3C3D3E3F404142434445464748494A4B4C4D4E4F505152535455565758595A5B5C5D5E5F606162636465666768696A6B6C6D6E6F707172737475767778797A7B7C7D7E7F808182838485868788898A8B8C8D8E8F909192939495969798999A9B9C9D9E9FA0A1A2A3A4A5A6A7A8A9AAABACADAEAFB0B1B2B3B4B5B6B7B8B9BABBBCBDBEBFC0C1C2C3C4C5C6C7C8C9CACBCCCDCECFD0D1D2D3D4D5D6D7D8D9DADBDCDDDEDFE0E1E2E3E4E5E6E7E8E9EAEBECEDEEEFF0F1F2F3F4F5F6F7F8F9FAFBFCFDFEFF
			 | 
		
					 äöü    000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F202122232425262728292A2B2C2D2E2F303132333435363738393A3B3C3D3E3F404142434445464748494A4B4C4D4E4F505152535455565758595A5B5C5D5E5F606162636465666768696A6B6C6D6E6F707172737475767778797A7B7C7D7E7F808182838485868788898A8B8C8D8E8F909192939495969798999A9B9C9D9E9FA0A1A2A3A4A5A6A7A8A9AAABACADAEAFB0B1B2B3B4B5B6B7B8B9BABBBCBDBEBFC0C1C2C3C4C5C6C7C8C9CACBCCCDCECFD0D1D2D3D4D5D6D7D8D9DADBDCDDDEDFE0E1E2E3E4E5E6E7E8E9EAEBECEDEEEFF0F1F2F3F4F5F6F7F8F9FAFBFCFDFEFF
			 | 
		
					-ÄÖÜ    8FE95C725427
			 | 
		
					+ÄÖÜ    8FE95C0D5427
			 | 
		
					 drop table t1;
			 | 
		
| 
					 | 
		
					mysqltest: Result content mismatch
			 | 
		
It works on mysql 5.6.17.
Attachments
Issue Links
- relates to
 - 
                    
MDEV-12240 LOAD DATA INFILE binary blobs failing for UTF8
-         
 - Confirmed
 
 -