*Improved Fetch Plans* With OrientDB 2.1, we improved fetch plans to be much more powerful. Now you can specify (it's optional) at which level(s) the rules apply. You can specify a level, a range or * for any. Levels starts from 0.
Examples: - *[*]in_*:-2* -> avoid fetching incoming edges at any level - *[0-3]out_*:1* -> fetches outgoing edges up to 4th level - *[1]out_Follows:2* -> fetches outgoing edges of type "Follows" only on 2nd level up to the 4th level - *[1-]out_FriendOf:1* -> fetches outgoing edges starting from 2nd level with no limit - *"[*]out_*:1 [*]in_*:-2"* -> fetches outgoing edges with no limits, and never incoming edges I hope this will make your life simpler ;-) You can find it in "develop" branch, or Sonatype as soon as our Jenkins build and deploy the distribution online. For more information: https://github.com/orientechnologies/orientdb/wiki/Fetching-Strategies Lvc@ -- --- 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.
