Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So do you need a new node in the graph, or a copy of the Django model?</p> <p>To create a copy with the same properties (but not the same relationships) and a new in-graph node, you could try something like</p> <pre><code>p = Person.objects.create(name="John Doe") p2 = Person.objects.create(**p.node.properties) </code></pre> <p>Doing the same thing with relationships is a little more difficult, but I've done it in the past and can write up a gist if that's what you need. Alternatively, this could also all be done in Gremlin or Cypher (with neo4django's helper functions) if that's a better fit, eg</p> <pre><code>from neo4django.db import connection p = Person._neo4j_instance(connection.gremlin('results=&lt;some code that yields a copied node&gt;')) </code></pre> <p>If you just need a copy of the Django model that's a different Python object (but still attached to the same node) you might try</p> <pre><code>&gt;&gt;&gt; p = Person.objects.create(name="John Doe") &gt;&gt;&gt; p2 = Person.from_model(p) &gt;&gt;&gt; print p2.name John Doe </code></pre> <p>HTH!</p> <p>EDIT:</p> <p>How could I have forgotten- there's an included convenience method for this!</p> <pre><code>&gt;&gt;&gt; john = Person.objects.create(name="John Doe") &gt;&gt;&gt; john_2 = john.copy_model() &gt;&gt;&gt; john.name == john_2.name True </code></pre> <p>Relationships and properties are all copied, though the returned model is unsaved- they don't share a node in the graph.</p> <p>Sorry about the run around, maybe this will be a little easier. </p>
    singulars
    1. This table or related slice is empty.
    1. POcopying / cloing neo4django model object
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMatt Luongo
    1. USMatt Luongo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POcopying / cloing neo4django model object
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COActually I wanted _eventually_ a new node in the graph. However, I want to edit (some of) the properties (and relationships) before saving the new node.
      singulars
      1. PO
      1. USA Sz
    2. COSo your first suggestion (**p.node.properties) helps. I would appreciate the offered Gist for properties (or can it more ore less be achieved with a for...in loop?)
      singulars
      1. PO
      1. USA Sz
    3. COIt's basically a loop over fields in the `Person._meta.fields` list. Fields that are a subclass of `neo4django.db.models.relationships.MultipleNodes` and `SingleNode` are the fields for the many and one side of a relationship, and you can get things like their name. I'll post a gist if that isn't clear enough- I'd be surprised if it is ha.
      singulars
      1. PO
      1. USMatt Luongo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload