Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add hyperedges #7

Open
5 of 7 tasks
cassinius opened this issue Sep 30, 2020 · 2 comments
Open
5 of 7 tasks

add hyperedges #7

cassinius opened this issue Sep 30, 2020 · 2 comments

Comments

@cassinius
Copy link
Owner

cassinius commented Sep 30, 2020

  • class hyper-edge spanning 3 defined node classes
  • has an internal definition of its 3 connected node types
    => implicitly via the node objects it is handed..
  • has an internal definition of its 3 connecting edge types
  • HE takes a hypernode feature object and an info edge features object
  • decouple entity from ArangoNode, derive from entity & define own CRUD methods on it
  • transactions? rollback?
  • test cases?
@cassinius
Copy link
Owner Author

cassinius commented Oct 1, 2020

  • Re-structure base classes, so that we can use a custom object type as the create methods argument
    • don't violate Liskov's substitution principle...
    • static async create<C extends HE3CreateCfg, T extends ArangoHyperEdge3>(cfg: C): Promise
      => DONE by introducing a BaseDoc class which derives from Entity and implements CRUD methods for Nodes & Edges, but not for HyperEdge

@cassinius
Copy link
Owner Author

cassinius commented Oct 20, 2020

right now, we cannot query an edge by _from & _to, combined; this is a problem with duplicate edge creation, which at the moment only leaves us the choice to -) use create & either catch the Error or ignore it... introduce either:

  • uniqueAttr: [_from, _to] for all edges, so we can use upsert => but do we want that in any case within hyperedges??
    => no!
  • write an edge-specific byNodes query which takes _from & _to as arguments, so we can implement it in a 2-step process

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant