Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Better Error Reporting on CSV Import #564
When importing a large CSV file Postico can report errors at a row level which is good. However, it would be much better if it showed the row in question so that the error could be properly debugged.
Here we can see a problem with row 336797. In vi this row looks to be perfectly fine and there is no character 'L' on that row. So it may be that postico has calculated a different row number? It would be easier to troubleshoot if we could see the data concerned.
Hi @citizenfish! Thanks for the bug report.
Is it possible that there are some non-standard line break characters in the file?
Is there any chance you can send us a copy of the file (either to firstname.lastname@example.org or to my personal email address email@example.com). If not, is it possible to create an extract of the file that still exhibits the problem, but does not contain confidential data?
OK, it looks like we're counting rows wrong. The problem is actually in line 28068.
We'll fix the bug next week!
As for displaying the problematic row, that would of course be very convenient, but right now Postico is configured to only show a 1MB preview of the file for performance reasons. If the error is later in the file, we can't show it. I need to think about this.
We've fixed this in build 2991, which you can download here: https://eggerapps-downloads.s3.eu-west-1.amazonaws.com/postico-2991.zip
Postico now reports the correct line number, and the error message also includes the value that could not be converted to a number, which is hopefully more helpful.
Thanks again for reporting this issue!