1
CSV Critical Issues
Source: supabase/supabase#9789 · opened by @FuadEfendi
There are few *critical* configuration issues making this feature not-compatible with CSV conventions:
• where is text file encoding configuration field? UTF-8, and etc.
• where is Quote Character configuration?
• where is column separator configuration?
• skip 1st data row (headers) vs. not-skip?
And so on. For example, my CSV contains quoted multi-line fields, and existing CSV importer recognizes it as multiple rows instead of single row with multiline fields.
• where is text file encoding configuration field? UTF-8, and etc.
• where is Quote Character configuration?
• where is column separator configuration?
• skip 1st data row (headers) vs. not-skip?
And so on. For example, my CSV contains quoted multi-line fields, and existing CSV importer recognizes it as multiple rows instead of single row with multiline fields.
No pledges yet. Be the first to back this.
Comments
Similar requests
Add CSV Delimiter Configuration Option
5 votes · 0 comments
Support skipping conflicting rows during CSV import
1 vote · 0 comments
CSV Import in studio fails to assign authenticated user id
0 votes · 0 comments
Studio CSV import: skip type mismatched rows and download rejects
1 vote · 0 comments
Please update image with no vulnerability
4 votes · 0 comments
No comments yet.