One of the things that caught my attention about orientDB (I've started to 
play with it for some weeks (community 2.0.8  and enterprise 2.0.8 and 
beta)) is the fact that you can just link the data across multiple tables 
(classes) and then just retrieve the data by using fetch strategies or so 
it said on the description of orient.

So far I really haven't been able to get a graph traverse result that I can 
be happy with.

Now I'm aware that the fetchplan is to be used on remote connection and 
rest calls.

Going to the VehicleHistoryGraph example database I just wanted to do a 
simple db traverse and get everything that is associated with one of the 
"car makes" that is listed under class Make. so when I do: 
http://127.0.0.1:2480/documentbyclass/VehicleHistoryGraph/Make/606/*:-1
I don't get a result that is really fetching all the incoming edges and all 
the outgoing edges just go unfetched.

*so without fetching:*
http://127.0.0.1:2480/documentbyclass/VehicleHistoryGraph/Make/606

{"@type":"d","@rid":"#15:606","@version":129,"@class":"Make","name":"Plymouth","in_isMake":["#25:1761","#25:1813","#25:1976","#25:1998","#25:2014","#25:2081","#25:2137","#25:2155","#25:2216"],"out_Sold":["#22:5143","#22:5219","#22:5621","#22:5739"],"@fieldTypes":"in_isMake=g,out_Sold=g"}

*with fetching strategy:*
http://127.0.0.1:2480/documentbyclass/VehicleHistoryGraph/Make/606/*:-1

I would expect all of the 9 incoming edges (in_isMake) to be "resolved" 
that is fetched in the result, but 3 of them just do not (#25:2081, 
#25:2155, #25:2216)
and for the outgoing edges (out_Sold) I get: 
"out_Sold":["#22:5143","#22:5219","#22:5621","#22:5739"] as a response so 
it is not even trying to fetch those links at all.

*I have tried from studio* with same missing results

select @this.toJSON('fetchPlan:*:-1') from Make WHERE name='Plymouth'

select * from Make WHERE name='Plymouth' FETCHPLAN *:-1

select * from Make WHERE name='Plymouth' FETCHPLAN [*]*:-1
-----> This one fetches nothing

select * from Make WHERE name='Plymouth' FETCHPLAN in_*:-1 out_*:-1

*from dbVisualizer 9.2.5 free (JDBC driver 2.0.8 all)*

SELECT * FROM Make where name='Plymouth' FETCHPLAN *:-1

I get:
Name         in_isMake out_Sold
Plymouth    [size=9]    [size=4]


So i've tried http, remote (JDBC), local (studio)

I really don't see how to go around with these fetch strategies which 
supposedly are paramount to what OrientDB can offer when compared to mongo 
(and SQL for that matter)
Does this only work if you are actually willing to code using the JAVA API? 
or Do i need to learn Gremlin to get that thing done? 
 
thank you !


-- 

--- 
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.

Reply via email to