MariaRocks port: update test result for rocksdb.rocksdb_parts

- EXPLAIN is different
- error message is
- the output order is different, because MySQL knows when to use
  ha_partition::handle_unordered_scan_next_partition.
  Reading the table data without any ordering happens to produce
  MariaDB uses  ha_partition::handle_ordered_index_scan for this index
  scan (this is a deficiency), which causes it to produce the row with
  pk=1 first.


  MariaDB uses

storage/rocksdb/mysql-test/rocksdb/r/rocksdb_parts.result

@@ -47,11 +47,11 @@ insert into t1 values (11,20,20);
 insert into t1 values (12,20,20);
 explain select * from t1 force index(col1) where col1=10;
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
-1	SIMPLE	t1	ref	col1	col1	5	const	2000	NULL
+1	SIMPLE	t1	ref	col1	col1	5	const	2000	
 select * from t1 force index(col1) where col1=10;
 pk	col1	col2
-2	10	10
 1	10	10
+2	10	10
 select * from t1 use index () where col1=10;
 pk	col1	col2
 2	10	10
@@ -94,7 +94,7 @@ drop table t1, t2;
 CREATE TABLE t1 (c1 INT NOT NULL, c2 CHAR(5)) PARTITION BY HASH(c1) PARTITIONS 4;
 INSERT INTO t1 VALUES(1,'a');
 RENAME TABLE t1 TO db3.t3;
-ERROR HY000: Error on rename of './test/t1' to './db3/t3' (errno: 122 - Internal (unspecified) error in handler)
+ERROR HY000: Error on rename of './test/t1' to './db3/t3' (errno: 122 "Internal (unspecified) error in handler")
 SELECT * FROM t1;
 c1	c2
 1	a