I'm working on a web application and I thought that moving to 2.1 would
make sense. A few things to note...
In order to prevent object property collisions in a query, I used an @
prefix in the AS clause of the select, i.e.
select in('PM_child') as @parent.
In 2.0 this wasn't a problem but in 2.1 it is. It's not too bad to change
everything but it caught me offguard.
The second is worse and confusing. If I put this query in the web
interface:
select @rid,*,in('PM_child') as PMt_parent from (traverse in('PM_child')
from [#37:0,#37:1])
It returns the expected results without a problem. However, in oriento,
even using exec() to work raw, orientdb throws an error:
2015-08-10 15:50:13:681 WARNI {db=gdp_server} Cannot serialize record:
pmLibrary#37:1{name:lib2,kind:library,uri:$(site:protocol)://$(site:connection)/depot/icm/proj/$(project)/$(variant)/$(vartype:dir)/lib2/...,in_PM_child:[#29:22],rid:#37:1,PMt_parent:[1]}
v2 [ONetworkProtocolBinary]
and the results are corrupted. Because of that I went back to 2.0.
What do you need from me help track down this problem? Is this an
incompatibility between oriento and orientdb 2.1 binary protocol?
Gary
--
---
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/d/optout.
