summaryrefslogtreecommitdiff
path: root/topics
diff options
context:
space:
mode:
authorMunyoki Kilyungi2024-04-30 14:39:19 +0300
committerMunyoki Kilyungi2024-04-30 14:39:19 +0300
commit087d3791845ffce8ea55fde514e076c5d74ab6fc (patch)
tree96c4aea829264f79eed2cf5078eed40de67e10b3 /topics
parent493954515b34888dee2622a8e6ae2dca47e7b4be (diff)
downloadgn-gemtext-087d3791845ffce8ea55fde514e076c5d74ab6fc.tar.gz
Minor updates.
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
Diffstat (limited to 'topics')
-rw-r--r--topics/gn-uploader/data-upload-validation.gmi2
1 files changed, 1 insertions, 1 deletions
diff --git a/topics/gn-uploader/data-upload-validation.gmi b/topics/gn-uploader/data-upload-validation.gmi
index 221cee5..8d005bb 100644
--- a/topics/gn-uploader/data-upload-validation.gmi
+++ b/topics/gn-uploader/data-upload-validation.gmi
@@ -21,7 +21,7 @@ I selected the suitable file type from the expression data options, whether aver
# Challenges Faced and Solutions
-During the data upload process, I encountered several challenges that required solutions. One challenge was identified as a database schema bug: a bug in which the "ProbeSetSE" has the column "StrainId" but with a different size integer (smaller) than that in table "Strain” which could cause errors when inserting data, if the strain exceeds the value 65535. The solution to this was to run a query to correct it against the database.
+During the data upload process, I encountered several challenges that required solutions. One challenge was identified as a database schema bug: a bug in which the "ProbeSetSE" has the column "StrainId" but with a different size integer (smaller) than that in table "Strain" which could cause errors when inserting data, if the strain exceeds the value 65535. The solution to this was to run a query to correct it against the database.
Another error surfaced during the dataset upload process: