Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-4718

Test "outfile_loaddata" fails on bigendian arches (ppc64)

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.5.31
    • Fix Version/s: 5.5.32
    • Component/s: None
    • Labels:
      None
    • Environment:
      Linux, ppc64

      Description

      I'm experiencing this problem with mariadb-5.5.31 on ppc64:

      main.outfile_loaddata                    [ fail ]
              Test ended at 2013-06-26 10:42:31
       
      CURRENT_TEST: main.outfile_loaddata
      --- /home/hhorak/rpmbuild/BUILD/mariadb-5.5.31-bad/mysql-test/r/outfile_loaddata.result	2013-05-21 18:09:51.000000000 -0400
      +++ /home/hhorak/rpmbuild/BUILD/mariadb-5.5.31-bad/mysql-test/r/outfile_loaddata.reject	2013-06-26 10:42:30.982084691 -0400
      @@ -143,15 +143,8 @@
       LOAD DATA INFILE 'MYSQLTEST_VARDIR/tmp/t1.txt' INTO TABLE t2 CHARACTER SET binary FIELDS TERMINATED BY 'ъ';
       Warnings:
       Warning	1638	Non-ASCII separator arguments are not fully supported
      -Warning	1265	Data truncated for column 'a' at row 1
      -Warning	1261	Row 1 doesn't contain data for all columns
      -Warning	1261	Row 1 doesn't contain data for all columns
      -Warning	1265	Data truncated for column 'a' at row 2
      -Warning	1261	Row 2 doesn't contain data for all columns
      -Warning	1261	Row 2 doesn't contain data for all columns
       SELECT * FROM t1 UNION SELECT * FROM t2 ORDER BY a, b, c;
       a	b	c
      -1	NULL	NULL
       1	ABC-АБВ	DEF-ÂÃÄ
       2	NULL	NULL
       SELECT * FROM t1 INTO OUTFILE 'MYSQLTEST_VARDIR/tmp/t1.txt' LINES STARTING BY 'ъ';
      @@ -181,7 +174,6 @@
       SELECT * FROM t1 UNION SELECT * FROM t2 ORDER BY a, b, c;
       a	b	c
       1	ABC-АБВ	DEF-ÂÃÄ
      -1	ABC-АБВ	DEF-ÂÃÄÑŠ2
       2	NULL	NULL
       # Default (binary) charset:
       SELECT * INTO OUTFILE 'MYSQLTEST_VARDIR/tmp/t1.txt' FROM t1;
       
      mysqltest: Result length mismatch

      I'm reporting this issue mostly because I think that ppc64 actually behaves correctly, while all other architectures don't and what's more – even .result file is generated incorrectly.

      The reason why I'm assuming that is straightly visible from the diff above – we have a valid cvs file (just generated) with multi-byte character as a separator. But we are not possible to load the data back – we get errors "Warning 1261 Row 1 doesn't contain data for all columns" and similar, which shouldn't be there at all in .results file.

        Attachments

          Activity

            People

            • Assignee:
              serg Sergei Golubchik
              Reporter:
              hhorak Honza Horak
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: