- 
                Notifications
    You must be signed in to change notification settings 
- Fork 35
Add data exception codes. Part 1. #186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
            NataliaIvakina
  merged 13 commits into
  neo4j:gqlstatus-errors
from
NataliaIvakina:data-exception-error-codes
  
      
      
   
  Oct 17, 2024 
      
    
  
     Merged
                    Changes from 9 commits
      Commits
    
    
            Show all changes
          
          
            13 commits
          
        
        Select commit
          Hold shift + click to select a range
      
      a6b8614
              
                Add data exception codes. Part 1.
              
              
                NataliaIvakina bdfa97a
              
                Replace tables with a descriptive list
              
              
                NataliaIvakina e935468
              
                Merge branch 'gqlstatus-errors' into data-exception-error-codes
              
              
                NataliaIvakina 203f7e3
              
                Update modules/ROOT/pages/errors/gql-errors.adoc
              
              
                NataliaIvakina b4370f8
              
                Update modules/ROOT/pages/errors/gql-errors.adoc
              
              
                NataliaIvakina 39f2c05
              
                Apply suggestions from code review
              
              
                NataliaIvakina e125f83
              
                Update gql-errors.adoc
              
              
                NataliaIvakina 494ad4e
              
                Replace backticks with curly brackets
              
              
                NataliaIvakina d2cef8e
              
                Update gql-errors.adoc
              
              
                NataliaIvakina 3b38f28
              
                Apply suggestions from code review
              
              
                NataliaIvakina 88acda6
              
                Comment out 22N17
              
              
                NataliaIvakina fbb0c06
              
                Add an intro on data exceptions
              
              
                NataliaIvakina 93b434c
              
                Apply suggestions from code review
              
              
                NataliaIvakina File filter
Filter by extension
Conversations
          Failed to load comments.   
        
        
          
      Loading
        
  Jump to
        
          Jump to file
        
      
      
          Failed to load files.   
        
        
          
      Loading
        
  Diff view
Diff view
There are no files selected for viewing
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              | Original file line number | Diff line number | Diff line change | 
|---|---|---|
|  | @@ -8,7 +8,7 @@ The following page provides an overview of all GQLSTATUS server error codes in N | |
| All errors in Neo4j have severity level `ERROR`. | ||
|  | ||
| * <<_connection-exceptions, Connection exceptions>> | ||
|  | ||
| * <<_data-exceptions, Data exceptions>> | ||
|  | ||
| [[_connection-exceptions]] | ||
| == Connection exceptions | ||
|  | @@ -97,4 +97,124 @@ Status description:: error: connection exception - alias chains are not permitte | |
|  | ||
| === 08N15 | ||
|  | ||
| Status description:: error: connection exception - no such routing policy. Policy definition of the routing policy { $routingPolicy } could not be found. Verify that the spelling is correct. | ||
| Status description:: error: connection exception - no such routing policy. Policy definition of the routing policy { $routingPolicy } could not be found. Verify that the spelling is correct. | ||
|  | ||
| [[_data-exceptions]] | ||
| == Data exceptions | ||
|  | ||
| The following is a list of the data exceptions that can occur in Neo4j. | ||
|         
                  Lojjs marked this conversation as resolved.
              Outdated
          
            Show resolved
            Hide resolved | ||
|  | ||
| === 22N00 | ||
|  | ||
| Status description:: error: data exception - unsupported value. The provided value is unsupported and cannot be processed. | ||
|  | ||
| === 22N01 | ||
|  | ||
| Status description:: error: data exception - invalid type. | ||
| Expected the value { $value } to be of type { $valueTypeOredList }, but was of type { $valueType }. | ||
|         
                  NataliaIvakina marked this conversation as resolved.
              Outdated
          
            Show resolved
            Hide resolved         
                  NataliaIvakina marked this conversation as resolved.
              Outdated
          
            Show resolved
            Hide resolved | ||
|  | ||
| === 22N02 | ||
|  | ||
| Status description:: error: data exception - specified negative numeric value. Expected { $option } to be a positive number but found { $value } instead. | ||
|  | ||
| === 22N03 | ||
|  | ||
| Status description:: error: data exception - specified numeric value out of range. Expected { $component } to be of type { $valueType } and in the range { $lower } to { $upper } but found { $value }. | ||
|  | ||
| === 22N04 | ||
|  | ||
| Status description:: error: data exception - invalid input value. Invalid input { $input } for { $context }. Expected one of { $inputOredList }. | ||
|         
                  NataliaIvakina marked this conversation as resolved.
              Outdated
          
            Show resolved
            Hide resolved | ||
|  | ||
| === 22N05 | ||
|  | ||
| Status description:: error: data exception - input failed validation. Invalid input { $input } for { $context }. | ||
|  | ||
| === 22N06 | ||
|  | ||
| Status description:: error: data exception - empty input string. Invalid input. { $option } needs to be specified. | ||
|  | ||
| === 22N07 | ||
|  | ||
| Status description:: error: data exception - invalid pre-parser option key. Invalid pre-parser option(s): { $optionList }. | ||
|  | ||
| === 22N08 | ||
|  | ||
| Status description:: error: data exception - invalid pre-parser combination. Invalid pre-parser option, cannot combine { $option1 } with { $option2 }. | ||
|  | ||
| === 22N09 | ||
|  | ||
| Status description:: error: data exception - conflicting pre-parser combination. Invalid pre-parser option, cannot specify multiple conflicting values for { $option }. | ||
|  | ||
| === 22N10 | ||
|  | ||
| Status description:: error: data exception - invalid pre-parser option value. Invalid pre-parser option, specified { $input } is not valid for option { $option }. Valid options are: { $optionAndedList }. | ||
|         
                  NataliaIvakina marked this conversation as resolved.
              Outdated
          
            Show resolved
            Hide resolved | ||
|  | ||
| === 22N11 | ||
|  | ||
| Status description:: error: data exception - invalid argument. Invalid argument: cannot process { $input }. | ||
|  | ||
| === 22N12 | ||
|  | ||
| Status description:: error: data exception - invalid date, time, or datetime format. Invalid argument: cannot process { $input }. | ||
|  | ||
| === 22N13 | ||
|  | ||
| Status description:: error: data exception - invalid time zone. Specified time zones must include a date component. | ||
|  | ||
| === 22N14 | ||
|  | ||
| Status description:: error: data exception - invalid temporal value combination. Cannot select both { $temporal } and { $component }. | ||
|  | ||
| === 22N15 | ||
|  | ||
| Status description:: error: data exception - invalid temporal component. Cannot read the specified { $component } component from { $temporal }. | ||
|  | ||
| === 22N16 | ||
|  | ||
| Status description:: error: data exception - invalid import value. Importing entity values to a graph with a USE clause is not supported. Attempted to import { $expr } to { $graph }. | ||
|  | ||
| === 22N17 | ||
|          | ||
|  | ||
| Status description:: error: data exception - invalid date, time, or datetime function field name. Cannot read the specified { $component } component from { $temporal }. | ||
|  | ||
| === 22N18 | ||
|  | ||
| Status description:: error: data exception - incomplete spatial value. A { $crs } POINT must contain { $mapKeyAndedList }. | ||
|         
                  NataliaIvakina marked this conversation as resolved.
              Outdated
          
            Show resolved
            Hide resolved | ||
|  | ||
| === 22N19 | ||
|  | ||
| Status description:: error: data exception - invalid spatial value. A POINT must contain either 'x' and 'y', or 'latitude' and 'longitude'. | ||
|  | ||
| === 22N20 | ||
|  | ||
| Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with { $crs } coordinate reference system (CRS) and { $coordinates } coordinates. Use the equivalent { $crs2 } coordinate reference system instead. | ||
|         
                  NataliaIvakina marked this conversation as resolved.
              Outdated
          
            Show resolved
            Hide resolved | ||
|  | ||
| === 22N21 | ||
|  | ||
| Status description:: error: data exception - unsupported coordinate reference system. Unsupported coordinate reference system (CRS): { $crs }. | ||
|  | ||
| === 22N22 | ||
|  | ||
| Status description:: error: data exception - invalid spatial value combination. Cannot specify both coordinate reference system (CRS) and spatial reference identifier (SRID). | ||
|  | ||
| === 22N23 | ||
|  | ||
| Status description:: error: data exception - invalid latitude value. Cannot create WGS84 POINT with invalid coordinate: { $coordinates }. The valid range for the latitude coordinate is [-90, 90]. | ||
|  | ||
| === 22N24 | ||
|  | ||
| Status description:: error: data exception - invalid coordinate arguments. Cannot construct a { $valueType } from { $coordinates }. | ||
|  | ||
| === 22N25 | ||
|  | ||
| Status description:: error: data exception - invalid temporal arguments. Cannot construct a { $valueType } from { $temporal }. | ||
|  | ||
| === 22N26 | ||
|  | ||
| Status description:: error: data exception - unsupported rounding mode. Unknown rounding mode. Valid values are: CEILING, FLOOR, UP, DOWN, HALF_EVEN, HALF_UP, HALF_DOWN, UNNECESSARY. | ||
|  | ||
| === 22N27 | ||
|  | ||
| Status description:: error: data exception - invalid entity type. Invalid input { $input } for { $var }. Expected to be one of { $valueTypeOredList }. | ||
|         
                  NataliaIvakina marked this conversation as resolved.
              Outdated
          
            Show resolved
            Hide resolved | ||
|  | ||
|  | ||
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Uh oh!
There was an error while loading. Please reload this page.