Hi guys! I was given a task to check could we migrate our document management database to OriendDB. So far I was playing with OriendDB, gremlin so see how it works. My question is should we move it at all, could all things that we can do now in rdbms be done in graph database? The main reason we are investigating this is: some stored procedures take too long to execute (because we have lots of data).
Our db model has many tables, some of them are just connecting tables (n:n relationship), but they all have one thing in common: no foreign keys! When we query the data we use case numbers, document numbers and another "numbers" to connect data. These numbers sometimes are not unique per table (we have 'deleted' or 'active' columns that we use in our queries). I managed to import some data, it went ok, importing of edges was extremely slow, so instead of that I tried to create links between classes but it failed because of this "uniqueness reason". And stored procedure that I have to "translate" to gremlin uses joins heavily (and it has about 150 lines of code). Since I can not create links, creation of edges lasts too long, how to use gremlin to traverse data at all? And let's say that I create edges and links somehow so I can translate my stored procedure, what should I do when I have to translate new stored procedure which uses totally different join expressions? My question is should all these make sense? -- --- You received this message because you are subscribed to the Google Groups "OrientDB" 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.
