Hi!
I looked into configuration files of 3.0.0-SNAPSHOT and all of a sudden, I
discovered that there is no mention of *node_auto_index* and
*relationship_auto_index* anymore (???)
Is this functionality removed completely, or maybe it is present but not
documented and there is no sample config
Thanks so much Luanne for all the info/explanation!
> SDN uses the internal Neo4j node or relationship ID to track domain
entities. This is the same as in the Neo4j browser.
> the loading of Jon - the 'id' is indeed the internal node id.
Whoa... wait, I thought programs relying on internal
No, there are no constraints on rels.
What's your use-case? Do you have an actual performance problem?
Michael
> Am 23.03.2016 um 09:49 schrieb kincheong lau :
>
> Thanks! I was thinking adding unique property and then create
> index/constraint might improve
Hi everybody,
*JCypher* *3.3.0 *has been released.
New in this release:
- Query DSL - DETACH DELETE now supported.
- JSON Facade in preparation to access JCypher from other, possibly
remote, systems.
Release cycles have slowed down a bit, this is because I am working on a
new
for each existing 'product' that 'inside' a 'category', I would like to add
a property in relationship 'product->category'. When I run below cypher, it
create a new relationship instead of adding new property in the existing
one...how can I make it 1 relationship only?
1) Existing
> MATCH (p:Product)-[r:inside]->(c:Category)
SET r.type = p.id + '->' + c.id
But I strongly recommend against setting this kind of property !!
As you can always compute the information!
> MATCH (p:Product)-[r:inside]->(c:Category)
RETURN p.id + '->' + c.id
MERGE always tries to find the
Thanks! I was thinking adding unique property and then create
index/constraint might improve performance, would that be the case?
On Wednesday, March 23, 2016 at 3:53:31 PM UTC+8, Michael Hunger wrote:
>
> MATCH (p:Product)-[r:inside]->(c:Category)
>
> SET r.type = p.id + '->' + c.id
>
> But