diff options
author | V Narayanan <v.narayanan@sun.com> | 2009-12-03 17:18:43 +0530 |
---|---|---|
committer | V Narayanan <v.narayanan@sun.com> | 2009-12-03 17:18:43 +0530 |
commit | a5aa3b3c919ab53cdcaa657a6446051348371245 (patch) | |
tree | 93acd035717949e4567c97f47e5ade78fe2f641c /mysql-test/t/subselect_debug.test | |
parent | 40ec012c905be0262ba5c36bbccfa0db0105e31f (diff) | |
download | mariadb-git-a5aa3b3c919ab53cdcaa657a6446051348371245.tar.gz |
Bug#40814 CSV engine does not parse \X characters when they occur in unquoted fields
When a .CSV file for table in the CSV engine contains
\X characters as part of unquoted fields, e.g.
2,naraya\nan
\n is not interpreted as a new line (it is however interpreted as a
newline in a quoted field).
The old algorithm copied the entire value for a unquoted field without
parsing the \X characters.
The new algorithm adds the capability to handle \X characters in the
unquoted fields of a .CSV file.
mysql-test/r/csv.result:
Bug#40814 CSV engine does not parse \X characters when they occur in unquoted fields
Contains additional test output corresponding to the new
tests added.
mysql-test/t/csv.test:
Bug#40814 CSV engine does not parse \X characters when they occur in unquoted fields
Contains additional tests for testing the behaviour of the CSV
storage engine when the fields are not enclosed in quotes and
contain \X characters.
storage/csv/ha_tina.cc:
Bug#40814 CSV engine does not parse \X characters when they occur in unquoted fields
Changes the parsing logic of the rows in a CSV file, to parse
\X characters that might be present in the unquoted fields.
Diffstat (limited to 'mysql-test/t/subselect_debug.test')
0 files changed, 0 insertions, 0 deletions