summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBonfaceKilz2022-04-11 13:26:21 +0300
committerBonfaceKilz2022-04-11 13:26:21 +0300
commit0372522c5ba0382bc0e16b73aeb5771db2ec5887 (patch)
treeeea67747d2244c764c6781688ee0432763311160
parentc55913f3a5d63e4418eb67ec3bdb65b343d4ca6b (diff)
downloadgn-gemtext-0372522c5ba0382bc0e16b73aeb5771db2ec5887.tar.gz
Update issue on ITP_10001-longevity-data-set
-rw-r--r--issues/csv-error-ITP_10001-longevity-data-set.gmi24
1 files changed, 22 insertions, 2 deletions
diff --git a/issues/csv-error-ITP_10001-longevity-data-set.gmi b/issues/csv-error-ITP_10001-longevity-data-set.gmi
index 4200721..830f96d 100644
--- a/issues/csv-error-ITP_10001-longevity-data-set.gmi
+++ b/issues/csv-error-ITP_10001-longevity-data-set.gmi
@@ -22,10 +22,30 @@ The screenshot:
## Tasks
-- [ ] Reproduce the issue
+- [X] Reproduce the issue
-- [ ] Check if database is affected in any way
+- [X] Check if database is affected in any way
- [ ] Send a patch to fix
- [ ] Notify every relevant user
+
+## Notes
+
+### Mon 11 Apr 2022 13:19:14 EAT:
+
+The CSV file is technically fine. In that database, some characters are inserted with control sequences that need to be stripped out. Here's a current snip of how that looks like:
+
+```
+JL00005,896.000000,x,x,896,4/22/04,,4OHPBN_J,Oct,,0^M,M,JL,1,2004
+JL00006,1077.000000,x,x,1077,4/22/04,,4OHPBN_J,Apr,,0^M,M,JL,1,2004
+JL00007,790.000000,x,x,790,4/22/04,,4OHPBN_J,Jun,,0^M,M,JL,1,2004
+JL00032,916.000000,x,x,916,4/21/04,2017.06,Cont_04_J,Oct,M,2^M,M,JL,0,2004
+JL00033,1099.000000,x,x,1099,4/21/04,,Cont_04_J,Apr,,0^M,M,JL,0,2004
+```
+
+Notice the "^M" represents a carriage return. See:
+
+=> https://en.wikipedia.org/wiki/ANSI_escape_code#C0_control_codes
+
+When storing case attributes, values with control sequences are also stored, and when you download that data for use, they were not being stripped out. As a consequence, opening the csv file in Excel (or similar) software resulted in data that seems jumbled up.