QueryResponse was initially designed with triggers in mind where triggers only respond to one of either a node or relationship. But QueryResponse is just a message class and also delivers database responses to the job launcher. Should the job launcher be more flexible in supporting multiple relationships? My initial impression is yes, since we want to support a wide array of jobs.
QueryResponse was initially designed with triggers in mind where triggers only respond to one of either a node or relationship. But QueryResponse is just a message class and also delivers database responses to the job launcher. Should the job launcher be more flexible in supporting multiple relationships? My initial impression is yes, since we want to support a wide array of jobs.