Cyclic reference check should be avoided if the fetch plan do not have infinite depth (cases where depth is greater or equal to 0).
What you think ? Regards, Gaurav On Apr 20, 2014 3:00 PM, "Gaurav Dhiman" <[email protected]> wrote: > Hi Luca, > > Thanks for response. > > Yes I knew that its done to avoid cyclic reference else fetch will for in > infinite loop. > > My point is, this check for cyclic reference should only be applied if > infinite depth (-1) is given in fetch plan. Also as you suggested, > additional option to avoid cyclic check can also be given but that will be > prone to user errors, if cyclic check is avoided in case of infinite depth. > > I will create the feature request in bug system. Is thee some workaround > for now. I am using 1.7rc1 version. > > Regards, > Gaurav > On Apr 20, 2014 2:19 PM, "Luca Garulli" <[email protected]> wrote: > >> Hi Gaurav, >> this is to avoid cyclic references. Think to the case you've the same RID >> in your graph: it would be recursively infinite. But in your case could >> have sense to just always expand records even if already expanded. >> >> AFAIK we don't have such setting on fetch-plan. May you create a new >> issue? It's very easy to implement it. >> >> Lvc@ >> >> >> >> On 19 April 2014 11:36, Gaurav Dhiman <[email protected]> wrote: >> >>> How to fetch all related records (LINK / LINKSET) in a case if two or >>> more links point to same record ? >>> >>> *Example:* >>> Lets say the class (A) have links createByUser, modifiedByUser and >>> allUsers pointing to same record (#10:3) of OUser class. >>> >>> If we specify FETCHPLAN ("*:-1") to fetch deep level records, only one >>> link is expanded (allUsers), rest other two (createByUser, >>> modifiedByUser) are not expanded. The reason for this is that all three >>> link points to same OUser record. >>> >>> SELECT FROM A FETCHPLAN *:-1 >>> >>> *Query:* >>> In above case, how to expand all three links even if they are pointing >>> to same record ? >>> >>> Regards, >>> Gaurav >>> >>> -- >>> >>> --- >>> 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. >>> >> >> -- >> >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "OrientDB" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/orient-database/KWF1qYr2yNk/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- --- 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.
