Wow, I wonder what it might be about this simple question going unanswered!
Can anyone confirm you can go, somehow, around this and retrieve the entirety of data for that record(everything linked, nested resolved and fetched) in the example database VehicleHistoryGraph as pointed out or if on the contrary we're talking about something in the current fetching capabilities of the DB (I've seen they've been improving it steadfastly and I wonder whether If they're still away from a point where the functionality is complete) so as to prompt the development guys to get note of this? *PD:I'd need to get to know how to open a bug towards them* El lunes, 4 de mayo de 2015, 17:01:18 (UTC-5), [email protected] escribió: > > 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 was said on the description of orient. > > So far, I really haven't been able to get that done, neither by a graph > traverse (this just gives me all the records associated) nor by a fetch > strategy query, there's no 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 fetched query 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 of the incoming edges, > and all of the outgoing edges just go unfetched altogether. > > *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 ! > > > > > *PD: -- Obviously doing traverse * from <class> WHERE <property>=<Value> > just gives me all the records associated but I'm not looking to visualize > 4k+ records on a graph I'm looking for a retrieval of all the linked data > for a records on a table in the way it is actually linked.-- I already have > tried with a smaller, less complicated db.-- I have already searched the > group and the web for this and haven't come across the solution nor the > explanation.* > -- --- 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.
