Export issues: CSV charset error, XSLX doesn't work
Hi there!
The CSV export seems to not be taking in consideration the charset? I exported some info that has special chars like á,é,í,ó,ú,ñ () and it shows is something like "Máximo" instead of "Máximo". There's attached an example from the Neon's SQL editor UI and the Excel UI.
Also, the XLSX export button does nothing, seems that it is not work at all. The Browser Console throws an error, which I also attach.
Please let me know if there's any other information that you guys need to troubleshoot this.
Thanks!
5 Replies
rival-black•13mo ago
Hey! Thank you for reporting this issue. I shared it with the team 🫡
Will report back once I hear back from them
deep-jade•13mo ago
Like @Mahmoud said, thanks for reporting this.
On the CSV issue, can I ask what character set your database is set to use?
And for the XLSX export problem, are you able to share some data and a query for which trying to export the result as XLSX gives you this error? And can I check which browser, browser version and OS you're using?
deep-jadeOP•13mo ago
CSV: We are using UTF-8. We can see the information correctly on both the UI and in our app, it’s the export that is failing (and didn’t before, like a month we did the same export and those chars had no issues).
XLSX: The query is “SELECT * FROM client WHERE active=true ORDER BY _id ADC;”, but happens on other tables and queries too. Browser: Google Chrome, Version 103.0.5060.134 (Official Build) (x86_64), on macOS 10.12
deep-jade•12mo ago
OK. On the CSV issue, can you try opening the exported CSV file in a text editor where you can specify the encoding, and set that explicitly to UTF8 (e.g. in Sublime Text, you'd use
Re-open with Encoding...)? I'd like to see more clearly whether the issue is with our CSV export, or with Excel wrongly detecting the character encoding. (Or did you already specify the character encoding as UTF8 when importing the CSV into Excel?)
On the XLSX: those are quite old versions of Chrome and MacOS. On the other hand, I just tested XLSX export (in general) on Chromium 103 and didn't have any problems. Can you provide a combination of query and data that fails? Without that, it's difficult for me to reproduce the issue.
@Jimmy Adaro Are you able to help with the queries above? I'm happy to look into this, but since I don't see the issue locally I kind of need this feedback.deep-jadeOP•12mo ago
Sorry for the delay, we’re pivoting and i forgot about this.
CSV, it’s weird because that Unicode error didn’t happen before, so I’m not use if it’s an error on my end or yours. Will try the explicit charset later today and let you know.
XLSX, same thing, that didn’t happen before (like a couple months ago), plus there’s that console log erro so I’m guessing it’s something on your end?