Initial new gql error codes for load csv (buffered char reader) exceptions.

Author: fastlag

modules/ROOT/content-nav.adoc

@@ -145,6 +145,9 @@
 **** xref:errors/gql-errors/22NA9.adoc[]
 **** xref:errors/gql-errors/22NAA.adoc[]
 **** xref:errors/gql-errors/22NAB.adoc[]
+**** xref:errors/gql-errors/22NAC.adoc[]
+**** xref:errors/gql-errors/22NAD.adoc[]
+**** xref:errors/gql-errors/22NAE.adoc[]
 **** xref:errors/gql-errors/22NB0.adoc[]
 **** xref:errors/gql-errors/22NB1.adoc[]
 **** xref:errors/gql-errors/22NB2.adoc[]

modules/ROOT/pages/errors/gql-errors/22NAC.adoc

@@ -0,0 +1,33 @@
+= 22NAC
+
+== Status description
+error: data exception - characters after quote in CSV field. At `{ <<input1>> }` @ position `{ <<pos>> }` - there's a field starting with a quote and whereas it ends that quote there seems to be characters in that field after that ending quote. That isn't supported. This is what was read: `{ <<input2>> }`.
+
+== Explanation
+When a CSV file has a field that starts with a quote has content after the ending quote that file is formatted incorrectly and trying to read such a file with `LOAD CSV` will result in an error.
+
+== Example scenario
+
+Given that `somefile.csv` is a CSV file with the following content:
+`
+x,y
+"x",1
+"y"y,2
+`
+Then running the query;
+----
+LOAD CSV 'somefile.csv' AS line RETURN count(line)
+----
+
+The following error will be thrown:
+[source]
+----
+error: data exception - characters after quote in CSV field. At 'somefile.csv' @ position 14 - there's a field starting with a quote and whereas it ends that quote there seems to be characters in that field after that ending quote. That isn't supported. This is what I read: 'y"y'
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/22NAD.adoc

@@ -0,0 +1,33 @@
+= 22NAD
+
+== Status description
+error: data exception - missing end quote in CSV field. At '{ <<input1>> }' @ position `{ <<dim1>> }` - Missing end for quote (\``{ <<input2>> }`\`) which started on line `{ <<dim2>> }`.
+
+== Explanation
+When a CSV file has a field that starts with a quote but misses an ending quote that file is formatted incorrectly and trying to read such a file with `LOAD CSV` will result in an error.
+
+== Example scenario
+
+Given that 'somefile.csv' is a CSV file with the following content:
+`
+x,y
+"x",1
+"y,2
+`
+Then running the query;
+----
+LOAD CSV 'somefile.csv' AS line RETURN count(line)
+----
+
+The following error will be thrown:
+[source]
+----
+error: data exception - missing end quote in CSV field. At 'somefile.csv' @ position 15 - Missing end for quote (\`"\`) which started on line 3.
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/22NAE.adoc

@@ -0,0 +1,35 @@
+= 22NAE
+
+== Status description
+error: data exception - multi-line field in illegal CSV context. At `{ <<input>> }` @ position `{ <<pos>> }` - Multi-line fields are illegal in this context and so this might suggest that there's a field with a start quote, but a missing end quote.
+
+== Explanation
+When a CSV file has a field that starts with a quote has content after the ending quote that file is formatted incorrectly and trying to read such a file with `LOAD CSV` will result in an error.
+
+== Example scenario
+
+Given that `somefile.csv` is a CSV file with the following content:
+----
+x,y
+"x",1
+"y
+",2
+----
+And that the neo4j database logging is configured with specific allowed multiline files, but where `somefile.csv` is not among them.
+Then running the query;
+----
+LOAD CSV 'somefile.csv' AS line RETURN count(line)
+----
+
+The following error will be thrown:
+[source]
+----
+error: data exception - multi-line field in illegal CSV context. At 'somefile.csv' @ position 15 - Multi-line fields are illegal in this context and so this might suggest that there's a field with a start quote, but a missing end quote.
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/index.adoc

@@ -584,6 +584,18 @@ Status description:: error: data exception - invalid list for property-based acc
 
 Status description:: error: data exception - mixed type list for property-based access control rule. The expression `{ <<expr>> }` is not supported. All elements in a list must be literals of the same type for property-based access control.
 
+=== xref:errors/gql-errors/22NAC.adoc[22NAC]
+
+Status description:: error: data exception - characters after quote in CSV field. At `{ <<input1>> }` @ position `{ <<pos>> }` - there's a field starting with a quote and whereas it ends that quote there seems to be characters in that field after that ending quote. That isn't supported. This is what was read: `{ <<input2>> }`.
+
+=== xref:errors/gql-errors/22NAD.adoc[22NAD]
+
+Status description:: error: data exception - missing end quote in CSV field. At `{ <<input1>> }` @ position `{ <<dim1>> }` - Missing end for quote (\``{ <<input2>> }`\`) which started on line `{ <<dim2>> }`.
+
+=== xref:errors/gql-errors/22NAE.adoc[22NAE]
+
+Status description:: error: data exception - multi-line field in illegal CSV context. At `{ <<input>> }` @ position `{ <<pos>> }` - Multi-line fields are illegal in this context and so this might suggest that there's a field with a start quote, but a missing end quote.
+
 === xref:errors/gql-errors/22NB0.adoc[22NB0]
 
 Status description:: error: data exception - invalid property-based access control rule involving `WHERE` and `IS NULL`. The property value access rule pattern `{ <<pred>> }` always evaluates to `NULL`. Use `WHERE` syntax in combination with `IS NULL` instead.