Giraldo Rosales wrote:
>
> Sure.
>
> It works perfectly when placing the value in the SQL directly. Where it
> inserts it incorrectly is when used with a prepared query. So in
> the GratefulDeadConcerts database, try:
> INSERT INTO V SET id=:id
>
> Then add the params:
> {"id":"6ce3ef04cb2cb750d4ce0d0f9648066f"}
>
> Then get the resulting record:
> SELECT * FROM V WHERE id ="6"
>
> You'll get back the incorrect record. Which is why I'm assuming it has
> something to do with the parsing of the prepared query.
>
When I try with the java driver in 1.6.4, it works:
ODatabaseDocument db = ODatabaseDocumentPool.global().acquire(
"remote:localhost/test", "admin", "admin");
Map<String,Object> parms = new HashMap<>();
parms.put("hash", "6ce3ef04cb2cb750d4ce0d0f9648066f");
Object result = db.command(new OCommandSQL("insert into test set
hash=:hash")).execute(parms);
System.out.println(result);
And the test class is created with "create class test".
regards,
Finn
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
