You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use parameter to insert vertex, nebula show me an error: -1005:Storage Error: The data type does not meet the requirements. Use the correct type of data.
#4375
Open
CorvusYe opened this issue
Jul 3, 2022
· 1 comment
When I use parameter to insert vertex, nebula show me an error: -1005:Storage Error: The data type does not meet the requirements. Use the correct type of data.
-1005:Storage Error: The data type does not meet the requirements. Use the correct type of data.
Others
When I invoke the method (com.vesoft.nebula.client.graph.net.Session#executeWithParameter), if the parameter is a vertex prop, the error happend too.
Reference other repo of nebula using in java, they use com.vesoft.nebula.client.graph.net.Session#execute to doing their work. For example nebula-jdbc and etc. Maybe it's this problem that stops them.
By the way, when we use string splicing to assemble stmt, it may cause a danger that supports nGQL injection I guess.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is a bug.
What happened?
When I use parameter to insert vertex, nebula show me an error: -1005:Storage Error: The data type does not meet the requirements. Use the correct type of data.
About my env
How To Reproduce
Steps to reproduce the behavior:
Tag of vertex
Set the parameter in Nebula Studio
Test the parameter
Insert vertex with parameters
Others
When I invoke the method (com.vesoft.nebula.client.graph.net.Session#executeWithParameter), if the parameter is a vertex prop, the error happend too.
Reference other repo of nebula using in java, they use com.vesoft.nebula.client.graph.net.Session#execute to doing their work. For example nebula-jdbc and etc. Maybe it's this problem that stops them.
By the way, when we use string splicing to assemble stmt, it may cause a danger that supports nGQL injection I guess.
The text was updated successfully, but these errors were encountered: