Does it make sense to create a graph with a very large amount edges between
vertices? For example if I have sellers and products as vertices and each
net user by buying something adding new edge (a edge from a seller to a
product with data and amount properties means that a seller sold a
Hi,
We have costumer in production which has 700 000 edges for one vertex and
does not experience performance problems so that is what graph databases
are intended for.
On Thu, Feb 6, 2014 at 9:24 AM, Tomek Kulakow tome...@gmail.com wrote:
Does it make sense to create a graph with a very large
Thank you:)
Could you tell me what about aggregation? Does OrientDB provide any
function to choose a subset of edges (with specyfic property) and make fast
addition for another property of edges in this set, or property of vertexes
in the set of pointed vertex.
I mean something like an
Hi,
There are group by in SQL and Gremlin, so you should chose what fits best
for you.
On Thu, Feb 6, 2014 at 2:18 PM, Tomek Kulakow tome...@gmail.com wrote:
Thank you:)
Could you tell me what about aggregation? Does OrientDB provide any
function to choose a subset of edges (with specyfic
https://github.com/orientechnologies/orientdb/wiki/SQL-Query
On Fri, Feb 7, 2014 at 9:08 AM, Andrey Lomakin lomakin.and...@gmail.comwrote:
Hi,
There are group by in SQL and Gremlin, so you should chose what fits best
for you.
On Thu, Feb 6, 2014 at 2:18 PM, Tomek Kulakow
