We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v. 2.2.13
Error: java.lang.IllegalArgumentException: Property value can not be null
java.lang.IllegalArgumentException: Property value can not be null
CREATE EDGE E FROM #21:20 TO #21:22 SET factor = 1e-06 Error: java.lang.IllegalArgumentException: Property value can not be null
CREATE EDGE E FROM #21:20 TO #21:22 SET factor = 1e-06
CREATE VERTEX V SET factor = 1e-06 -> factor has no value
CREATE VERTEX V SET factor = 1e-06
With the json syntax, it works:
CREATE VERTEX V CONTENT { "factor" : 1E-06 } CREATE EDGE E FROM #21:20 TO #21:22 CONTENT { "factor" : 1E-06 }
Note that this means that OrientDB-NET.binary doesn't work either since it doesn't use the json syntax.
The text was updated successfully, but these errors were encountered:
Fix parsing of double in scientific notation
11270f7
Resolves: #7013
Hi @tbertels
Fixed in branch 2.2.x, the fix will be released with 2.2.15.
It was a general problem related to parsing of numbers in scientific notation, not limited to CREATE EDGE
Thanks
Luigi
Sorry, something went wrong.
a317b8f
luigidellaquila
No branches or pull requests
OrientDB Version, operating system, or hardware.
v. 2.2.13
Operating System
Expected behavior and actual behavior
Error:
java.lang.IllegalArgumentException: Property value can not be null
Steps to reproduce the problem
CREATE EDGE E FROM #21:20 TO #21:22 SET factor = 1e-06
Error:
java.lang.IllegalArgumentException: Property value can not be null
CREATE VERTEX V SET factor = 1e-06
-> factor has no value
With the json syntax, it works:
Note that this means that OrientDB-NET.binary doesn't work either since it doesn't use the json syntax.
The text was updated successfully, but these errors were encountered: