Bug #61857 | Allow NULL fields in CSV engine | ||
---|---|---|---|
Submitted: | 13 Jul 2011 19:33 | Modified: | 14 Jul 2011 10:50 |
Reporter: | David Nuttall | Email Updates: | |
Status: | Open | Impact on me: | |
Category: | MySQL Server: CSV | Severity: | S4 (Feature request) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any | |
Tags: | null |
[13 Jul 2011 19:33]
David Nuttall
[13 Jul 2011 19:35]
David Nuttall
Also, once NULL fields are allowed again, NULL defaults would also need to be allowed.
[14 Jul 2011 10:51]
David Nuttall
Additional thoughts: While including #NULL# as a field is unambiguous as to what is intended, the NULL fields in a CSV file should also recognize empty fields. e.g. 4,"More words",-16.5,3,,"2011-07-14 08:26:15" There should be no spaces around the field separating commas, but the engine should be able to handle them if they do appear, such as when the table has been loaded with data from the OS. At this point, I recommend implementing the empty field over #NULL# place-holder in the CSV tables.