The neo4j graph database query language, cypher, can add nodes one at a time using a command like:
MERGE (n:NostrEvent {id:”abc123”})
But for a large number of nostr events, it’s much more performant to create a csv file, one row per event, and load them all at once with a command like:
LOAD CSV FROM 'file:////neo4jExport.csv' AS row MERGE (n:NostrEvent {id: row[0]})
In addition to the event id property, other properties can be included, e.g.:
pubkey: row[1], created_at: row[2], kind: row[3]
straycat / david
npub1u5…rldq3
2025-01-19 23:15:29
Author Public Key
npub1u5njm6g5h5cpw4wy8xugu62e5s7f6fnysv0sj0z3a8rengt2zqhsxrldq3Published at
2025-01-19 23:15:29Event JSON
{
"id": "f442ad97d57938a1d927679419a731e9f57525787a1bff9c48667aacb0971e91",
"pubkey": "e5272de914bd301755c439b88e6959a43c9d2664831f093c51e9c799a16a102f",
"created_at": 1737328529,
"kind": 1,
"tags": [],
"content": "The neo4j graph database query language, cypher, can add nodes one at a time using a command like:\n\nMERGE (n:NostrEvent {id:”abc123”})\n\nBut for a large number of nostr events, it’s much more performant to create a csv file, one row per event, and load them all at once with a command like:\n\nLOAD CSV FROM 'file:////neo4jExport.csv' AS row MERGE (n:NostrEvent {id: row[0]})\n\nIn addition to the event id property, other properties can be included, e.g.: \npubkey: row[1], created_at: row[2], kind: row[3]",
"sig": "03676dffc64779b1527c77a12010461159ca361771fa7174706ed378f343fbcf84321b45c94bdaacce2e8398455376c737befd1cb9f7db4b933c45dc956ece81"
}