orientdb: Update two vertex in batch mode leads to wrong result
OrientDb: 2.0.14
Orientjs
begin
LET t0 = UPDATE Node SET Points = 0
LET t1 = UPDATE Node SET Position = "admin"
return [$t0, $t1]
Result:
[ { classId: -2, value: null }, { classId: -2, value: null } ]
Expect somethink like this:
[ number, number ]
Result in 2.1.2 but in Studio
{
"result": [
{
"@type": "d",
"@version": 0,
"value": [
13,
13
]
}
],
"notification": "Query executed in 0.091 sec. Returned 1 record(s)"
}
BTW: It is very hard to take orientdb serious when such simple things doesn’t works. In almost every release there is a regression. Orientdb should be focused on qualitity not in features. This is my perspective in 6 month orientdb.
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 65 (32 by maintainers)
Commits related to this issue
- implementation of support for not record result set on binary protocol, issue #5091 — committed to orientechnologies/orientdb by tglman 8 years ago
- implementation of support for not record result set on binary protocol, issue #5091 — committed to orientechnologies/orientdb by tglman 8 years ago
@smolinari I added a note to the docs (not yet published, we will do it in short).
The HTTP protocol is a little bit slower than the binary one, because of the size of the messages, but the different is not significant compared to the whole elaboration
Thanks
Luigi