These are in regards to 3.0 if that makes a difference.
1) To confirm, graphs are not ever part of a Foxx app so if you have a
named graph in a database you have to access the vertices collection like
so:
const graphModule = require('@arangodb/general-graph');
const cityVenues = graphModule._graph('cityVenues');
cityVenues[module.context.collectionName('venues')].remove(venueKey);
Is this correct?
If so, is there a module.context variable that I can use to get the prefix
of the Foxx app? That way I can create the graph in the Foxx setup.js with
the matching prefix to the tables to ensure there is a graph per mounted
app if I need that.
2) Suppose I have three types of vertices: city, venue & event. Sometimes I
just need to access the city & venue parts of the graph and other times I
need to access all three. Assume the amount of city & venue only calls is
about the same as calls which need all three types.
What are the advantages/disadvantages of: 1 graph with all three vertices
or 2 graphs one of which has just city & venue and the other which has all
three?
Personally, I'm more concerned with read speed than write speed.
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
