okabasakal88

--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	05050000	01250500	05011000	--------	09990200	--------	--------	10100000	09990200	
--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	--------	06410200	--------	--------	--------	--------	10100000	10260000	01020000	10260000	09992600	09140000	07260900	10260000	07260100	10260000	09992600	09540100	10260000	
04670000	04670000	04670000	02010600	07260500	02010600	04670000	10100000	04670000	04670000	04670000	02010600	04670000	07130100	04670000	09992600	10030000	09992600	09250000	04670000	04670000	04790000	04670000	04230000	04670000	04670000	04670000	--------	--------	05011000	04670000	09992600	09250000	04670000	--------	--------	
--------	--------	07150400	04700000	04090000	0418

okabasakal88

Playing the Belgian Beer Graph into the Neo4j Browser!

For the past couple of years, I have been preaching the Neo4j gospel in many different places, meetups, conferences, and what have you. For the most part, I have been using a very specific demo that has been super well-received: The Belgian Beer Graph. It started out as a learning experience for me personally back in the day when Neo4j did not have any proper data import functionality - and I had to load the graph by jumping through all kinds of hoops.

And now: we can play this demo straight into the Neo4j browser. Such JOY!

okabasakal88

= SQL --> Neo4j

The main goal is to be able to import data from SQL (or similar RDBMS) into Neo4j, while maintaining Foreign Keys as relationships, using Cypher.  The reason behind using cypher vs. the batch importer is because I want to build a system that allows for multiple imports and updates without having to batch process it.

//console

= Table Structure Requirements:

1. Primary Key column names should use the pattern [TableName]+Id, so for a Contact table, the primary key field should be names ContactId.  This is to prevent overlap of Node Labels.

okabasakal88

FIAP NEO4J

NEO4J example script

This excercise was created from FIAP - MBA - Solution Architect

#####Create Social Network Node##### CREATE (Facebook:SocialNetwork { name:'Facebook'}) CREATE (Twitter:SocialNetwork { name:'Twitter'})