Intro to Graph Databases Episode #5 - Cypher, the Graph Query Language

[@qwertyuuytrewq825]

Great explanation! I think more people should see this.

[@benhutchison3828]

this is a quality tutorial, informative examples, well done Ryan 👏

[@klam77]

Very nicely explained. What a concept: querying GRAPHS!

[@chrisjanwust]

Quality video* and thoughtful examples. I started, very sceptical of this new AsciiArt query language, but after just this one video, I'm confident and excited to try it out. *Yeah, the volume is too low, had to use headphones.

[@MrLazini]

Very informative and clear to understand. Thanks!

[@veerlevanwinden6945]

At 7:58 at 'relationships have properties too' shouldn't the last bracket be square instead of a closing parenthesis?

[@nromaai2]

Theres a typo on the relationship slide, closing parenthesis should be closing square bracket `-[h:HIRED{type: 'fulltime'} *]* ->`

[@Ichinin]

Great tutorial, but @ 7:50, shouldn't -[:HIRED {type: 'fulltime'})-> be -[:HIRED {type: 'fulltime'}]-> ?

[@neo4j]

Ichinin Yes. absolutely. was going to correct it but required re-uploading video in youtube. then tried a “card” in youtube tho it had to be a link. i’ll see if i can pull something off as obviously it’s something people are noticing! thanks for the comment

[@TheWorldofAaron]

@@neo4j Thanks for verifying!

[@benogidan]

I just started going through these. These are the definition of hot fire I am looking to integrate with my Graphql queries

[@merridius2006]

audio is very low

[@ranjitpagale9395]

Enough to understand

[@ericb252]

12:05 of course Ann loves Dan, he's 5 years younger and driving his car!

[@parthsalat]

Thanks! This is a must watch video for beginners!

[@T_tolu]

Very detailed. Thank you for this.

[@tony7682]

@12:59 what do you mean "both of these queries SHOULD have the same performance"? Might there be a potential difference in how the two styles of queries perform?

[@neo4j]

Sorry, that was a nuance that I shouldn't have expressed. The queries are going to be interpreted by the Cypher language interpreter. The intent is that they have the same performance because the paths they take for processing are designed to be identical. However, due to the way query parsing works, there's a chance that new features could introduce differences, but those would be considered bugs and be resolved.

[@danielc6203]

4:44 - just a thought but shouldnt the Lives With relationship be going both ways - and that should be implied by the relationship type (i.e. if "Lives With" relationship type isnt possible unless it was going in both directions)

[@neo4j]

That's a good point. We could represent another relationship in the other direction, or assume bi-directionality, which is normally what you would do (as the extra relationship would always exist, so representing it in the graph is just using bytes that are unnecessary).

[@rubenco1253]

Hey this Ryan looks different! ;) thanks for the tutorials, they are very helpful, greetings from TU Delft

[@gnosis8142]

The real one was abducted by aliens, and this is a clone.

[@tanerkaya698]

There is a typo at 8:00 ? parenthesis closes instead of bracket

[@neo4j]

Thanks. Good catch. @lchinin (mentioned . below) and you both have great eyes! Cheers.

[@sazk4000]

it's been 3 years since this video and they still haven't fixed the audio issue. what does that tell you about the developers

[@ballu_jail_se_farar]

We created constraint on person node why it is not allowing to create name property on Dog node?

[@evraya1]

Thanks for the video. At the start of the syntax explanation it's stated that it can be hyphens or brackets. But never mentioned how exactly the hyphens variant works. Would be useful to know

[@neo4j]

We have a "Beginner's Guide to Cypher" which will go into just that detail. Please feel free to take a look neo4j.com/whitepapers/getting-started-with-cypher/

[@evraya1]

Neo4j thanks, that's useful. I've found Structr, searching for the app building with neo4j. May be you can recommend something in this regard too? Like a solution of working with the neo4j db which provides the front end and potential to be able to compose the app into iOS/Android and no code. Don't you know btw, Backendless uses Graph or relational db?

[@neo4j]

@@evraya1 I think this is a great conversation, but getting too lengthy for THIS forum. If you haven't already done so, please join us on our community.neo4j.com/ so we can have a good dialogue. See you there!

[@yaredterefe1508]

Great and high quality tutorial but so so so low volume for some reason

[@micknamens8659]

Why do you use singular when talking about the result of a query? It's a set of persons that Ann loves (or has loved) and a set of cars that she drives (or has been driving if you include historical data). Only if the query asks for the person she loves the most (needs a relationship weight property) or for her first car or the car she has been driving most often or for the longest total distance, the result is a single result or empty.

[@sudipg7666]

nicely explained thanks for the valuable time. your microphone might have some issue - audio is not much clear.

[@neo4j]

Thanks. Appreciate the feedback.

[@ThatNateGuy]

Hey, guys! Enjoying the videos, but one small critique: The audio on these videos is very low; they could do with some normalization. Very minor change. Thanks for uploading the content!

[@neo4j]

Nate Wynd thanks Nate. Ironically i actually lowered the volume of this one to avoid peaking. Will research the levels appropriate for youtube more!

[@bernardodc9631]

I thought that also.. in headphones with noise around is hard to hear

[@Saschaborg]

+Neo4j Try multiband compression followed by a limiter, that should solve all problems with levels or peaking :-) audio chain: EQ > MB Comp > Limiter

[@merts4376]

Great tutorial

[@merridius2006]

aren't relatonships named vertices?

[@ArielMeilij]

I still think the dog should be named "Pancho" :-)

[@accampellojr]

What happened to "helloooo?" I thought it was your trademark. But seriously, thank you for making these videos :) - very accessible introduction to neo4j.

[@neo4j]

Hah! How about Salve/Ciao/Hola/Alo/Selam ;-)

[@BodrumDrone]

After a long time I said the thats the point videos!

[@赵安东-b5j]

oh Ryan,your picture looks like bigger than before:)

[@anikethpaul3657]

Why the voice is so low?

[@Gandeloft]

You've been saying "SQL" as "sequel" and "query" as "curry" and that's been confusing me so much for some reason xD

[@neo4j]

Hi there.How do you pronounce SQL? Query as "curry" must be my Pennsylvania accent ;-)

[@Gandeloft]

Hi there.. I don't really. Not yet. I've just started to delve in to this whole thing, and have prior only heard the terms being used at my university where the professor pronounced "SQL" by spelling it, and as for query, well.. Slightly differently. XD I didn't mean anything bad.

[@chrisjanwust]

@@Gandeloft Well, that explains it. SQL is pronounced "sequel" in the industry (or at least, by all professionals I've had interaction with).

[@marekbernad7866]

please, record video again, the sound quality is awful, I have sound on 100% and hear just whispering....

[@ryguyrg]

Marek Bernád apologies for the low sound. however i’m not sure why sound at 100% is resulting in whispering for you. Listening at 50% on my iphone speaker is perfectly fine, though it’s a little light when wearing headphones. do you have a separate volume control for youtube vs your system sound?

[@marekbernad7866]

@@ryguyrg I am sorry... my speaker on computer suddenly stopped working correctly, on 50% possibility of its power now ... the video is fine on headphones... good tip, sorry again...

[@ryguyrg]

Marek Bernád no worries. the sound is low on the recording (right click, stats for geeks shoes -20db off of KZbin standard). so obviously bad, but not *that* bad ;-)

[@pabloastudillo1750]

speak up!

[@lerneninverschiedenenforme7513]

Please put a developer on the job. The actual content starts after 5 min. A real dev would've probably come to the point much better and the video would only take 10 minutes.

[@ryguyrg]

Thank you for your feedback. Apologies that you didn't find the background material helpful, but I assure you that I am a "real dev" with a degree in CS and 20+ years of coding experience.

[@lerneninverschiedenenforme7513]

@@ryguyrg "developer relations team" did sound more like a non-dev position to me. I appologize for the assumed surrounding words. I was too eager to find a quick-start guide. The main content stays valid , though: A short quick-start guide containing the absolute minimum of information to manipulate the db with a maximum of 2 seconds intro would've been very helpful.

[@ryguyrg]

@@lerneninverschiedenenforme7513 many DevRel teams, including ours, hire mostly engineers as it's important to relate to both internal and external developers. I understand that you want less intro material. Will take that into consideration for future videos. In this case, we included that intro material because we often see developers confused by "which interface to use," "why cypher vs what other databases use" and "if i learn this, will my skills be applicable to other DBs." And not understanding these can be a blocker or distraction to them learning Cypher.