You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove single relationships #5819 removes single element relationships. I understand the intention behind that. However, as already discussed in several tickets, e.g. here, the :1 relationship is a BIG and important thing (a Product has ONE Price and is produced by ONE Company).
Our API relies heavily on this feature. The release notes on v7 describe how to use the @cypher directive to achieve the removed behaviour. Since filtering on @cypher fields is possible, this seems to be working.
But that's only for READ scenarios. How about WRITE? It is not sufficient to just READ nodes connect in a :1 manner. We also have to CREATE, UPDATE, DELETE them. Is this coming as a new feature as proposed by me in Extend the @cypher directive with statements for create/update/delete mutations to be able to mutate properties which are resolved by a @cypher directive #1962? Or how are you planning to workaround WRITE scenarios?
But overall we are excited and look forward to v7! Is there an approximate timeline as to when we can expect a final release??
The text was updated successfully, but these errors were encountered:
Since the first alpha releases for API v7 are out, I want to share some thoughts on it.
Product
has ONEPrice
and is produced by ONECompany
).Our API relies heavily on this feature. The release notes on v7 describe how to use the
@cypher
directive to achieve the removed behaviour. Since filtering on@cypher
fields is possible, this seems to be working.But that's only for READ scenarios. How about WRITE? It is not sufficient to just READ nodes connect in a :1 manner. We also have to CREATE, UPDATE, DELETE them. Is this coming as a new feature as proposed by me in Extend the @cypher directive with statements for create/update/delete mutations to be able to mutate properties which are resolved by a @cypher directive #1962? Or how are you planning to workaround WRITE scenarios?
But overall we are excited and look forward to v7! Is there an approximate timeline as to when we can expect a final release??
The text was updated successfully, but these errors were encountered: