Hi Guys,
I think this feature will be useful, reason being, is you can have
more generic reltionship names e.g.
AuditCategoryNode->HAS_AUDIT->ClientNode<-IS_CLIENT
AuditCategoryNode->HAS_AUDIT->EmployeeNode<-IS_EMPLOYEE
So if I ran a report ONLY for audit nodes based on clients, it would
be nice to say get me all HAS_AUDIT where the node has an incoming
relationship IS_CLIENT.
Otherwise, it has to be done like this
AuditCategoryNode->HAS_CLIENT_AUDIT->ClientNode
AuditCategoryNode->HAS_EMPLOYEE_AUDIT->EmployeeNode
Thoughts guys? Would be nice to have a feature SIMILAR to gremlins
BACK statement, where you can traverse to CLIENT, go up to IS_CLIENT
and then kick a BACK step which filters out only CLIENTS :) I guess
this would have to be a subfilter, or perhaps it can currently be
done?
On May 2, 3:12 am, Andres Taylor <
andres.tay...@neotechnology.com>
wrote:
> On Tue, May 1, 2012 at 11:33 PM, Michael Hunger <
>