gt; RIGHT_NODE:#{RIGHT_LABEL} {LC_ID:{RIGHT_NODE}})
>
> If your label is fixed, eg. ":Document" then you can use it directly.
>
> Michael
>
>
> On Fri, Dec 5, 2014 at 2:34 AM, José F. Morales > wrote:
>
>> in your MATCH you _must_ provide the label then.
&
>
> in your MATCH you _must_ provide the label then.
>
>>
>> MATCH (LEFT_NODE:LABEL1 {LC_ID:{LEFT_NODE}}), (RIGHT_NODE:LABEL2 {LC_ID:{
>> RIGHT_NODE}})
>> ..
>>
>
> I have a node label whose header in the csv is called DESC with two values
> that for brevity are ... s and t .
> Do you mean I s
del can be improved. But I wanted to have a
really simple one to start. Time is a factor now. Those 5 are very much
qualities of the relationship. One of those properties applies only to one
two types of relationships.
> Michael
>
> On Fri, Dec 5, 2014 at 12:54 AM, José F. Morales
t the log output? :)
>
> use this: CREATE INDEX ON :{Label}(LC_ID); <- replace with your label(s)
>
> On Fri, Dec 5, 2014 at 12:09 AM, José F. Morales > wrote:
>
>> Andrii and Michael,
>>
>> Sorry for the delay in response. I was a little under the weather.
_ID]
Do I have this wrong? Should it have been CREATE INDEX ON :LC_ID?
Jose
On Monday, December 1, 2014 5:09:36 PM UTC-5, Andrii Stesin wrote:
>
> Hi José,
>
> On Monday, December 1, 2014 12:33:58 AM UTC+2, José F. Morales wrote:
>>
>> Ok, but how many valid dist
On Saturday, November 29, 2014 6:35:33 AM UTC-5, Andrii Stesin wrote:
>
> Hi Jose,
>
> On Saturday, November 29, 2014 1:12:52 AM UTC+2, José F. Morales wrote:
>>
>>
>>> 1. On nodes and their labels. First of all, I strongly suggest you to
>>> separa
ies has a
> label and a primary key of some sorts.
> It is just an optimization to not have to think about separate entities.
>
> Cheers, Michael
>
> On Sat, Nov 29, 2014 at 12:12 AM, José F. Morales > wrote:
>
>> Hey Andrii,
>>
>> I've been thinkin
- and Cypher
> silently stored their (supposed) numerics as strings. It's Ok, dude, you
> say it :) This led to confusion afterwards when say numerical comparisons
> doesn't MATCH and so on (though it's easy to correct with a single Cypher
> command, but anyway).
>
Hey Andrii !
Not yet, still trying to get the data with your and Michael's tips.
Anything major in this release? Something that helps with loading data
perhaps?
Happy turkeycide day!
Jose
On Thursday, November 27, 2014 10:38:07 AM UTC-5, Andrii Stesin wrote:
>
> Dear José, note that 2.1
That's awesome of you Andrii!! Thanks again!
Jose
On Thursday, November 20, 2014 11:02:35 AM UTC-5, Andrii Stesin wrote:
>
> I've had some painful experiences with massive data imports, so I hope my
> accumulated bumps and bruises will help someone else, too :)
>
> Good luck :)
> Andrii
>
--
Thanks Andrii,
I will let you know how it goes. I am trying to clean up the data some
more to get the size down right now. Probably will help I figure.
J
On Thursday, November 20, 2014 10:38:57 AM UTC-5, Andrii Stesin wrote:
>
> BTW if you need your nodes to have multiple labels each, I'd su
t;> Jose
>>
>> On Nov 17, 2014, at 3:35 PM, Kenny Bastani > > wrote:
>>
>> Hey Jose,
>>
>> Try turning off the object cache. Add this line to the neo4j.properties
>> configuration file:
>>
>> cache_type=none
>>
>> Then r
y label & property to connect them
> Make sure to have appropriate indexes / constraints
>
> You should also surround blocks if statements with begin and commit
> commands
>
> Von meinem iPhone gesendet
>
> Am 19.11.2014 um 04:18 schrieb José F. Morales Ph.D. >:
Any thing come of this?
Jose
On Thursday, October 4, 2012 10:22:57 PM UTC-4, Wes Freeman wrote:
>
> I've opened a feature request for Cypher, to allow conditional expressions
> of some sort. I think this would be a powerful way to provide a lot of new
> functionality.
>
> I'm bringing it up her
OK, upon Dan Greene's advise, here is some of the code I used to make the
database. This is only a small subset of the nodes and relationships.
CREATE (blor:Body_Location_or_Region:Anatomy:ANAT:UMLS{STY_RL:'Body
Location or Region',RT:'STY',UI:'T029',STN_RTN :'A2.1.5.2',EX :0,NH :'Y'})
CREATE
Hi Folks,
I need some help with the graphs that I derived after loading some data.
I created some data to load into my database that had about 85 nodes and
7k+ relationships. I loaded the data and it mostly seemed to work.
To create the data, I constructed my cypher code in a table as I fi
!) CREATE (Keanu)-[:ACTED_IN {roles:['Neo']}]->(TheMatrix)<--- source
is the v.2 server code for movies
2) CREATE (keanu)-[:ACTS_IN { role : 'Neo' }]->(matrix1)
<--- source is the v.2 manual code for movies p.28
I am not getting the significance of the []
;
> Neo4j 2.0.0 -
> (graphs)-[:FOR]->(everyone)<http://blog.neo4j.org/2013/12/neo4j-20-ga-graphs-for-everyone.html>
> Do something useful - Teach your kids 1 hour code! <http://code.org/learn>
>
>
> On Wed, Jan 1, 2014 at 5:26 AM, José F. Morales
>
Hello all,
I am a Neo4j newbie and am using neo4j to model some clinical data. I'll
refer to my graph db as the LC gdb. Further, the LC gdb will be influenced
by another database from NIH I'll refer to as "NIH.SM.
I decided to reformat the NIH.SM and import it into Neo4j for two reason
19 matches
Mail list logo
