min
min
Hi @michael-simons Just for confirm, I still need to hardcode the version with this way, right?
Anyone? @michael-simons
I don't get it. Why don't it just follow the define? In this case, just search for `CONTAIN` relation, like this ```` MATCH (myNode:`MyNode`) WHERE myNode.id = $__id__ OPTIONAL MATCH...
But someone like me need this. Also since SDN have cascade create/update already, I think provide this feature and default disable will be fine, isn't it?
> The `person1Repository` will query for `:Parent1_CONTAIN` nodes defined by `parent1Relationships` in `Parent1`. Those relationships are of type `BaseNode`. The next iteration will than query for `:Parent2_CONTAIN` and `:Parent1_CONTAIN` defined...
Any update? @michael-simons
> Having two spring data modules in place requires two transaction managers. Your solution is the way to go. As you have already found out, there was some trouble around...
> > I think spring data neo4j should fix this issue. > > To do the autoconfig is the main feature of starter, isn't it? > > Since I am...
(1) It's surprise to me that you can not comment Spring side things, Spring depend on jackson very heavily as I know. (2) Sad to heard that 😢 Also it...
(1) > Unless you were thinking I added Jackson-support in Spring? Yes....I thought such big level project will at least discuss with the author, instead just import it directly like...