Re[2]: [orientdb] Order By doesn't use indexes, slow performing when with a WHERE clause on just 150k rows

2015-08-17 Thread Sky Viker-Rumsey
Hi Luca Because this isn't a view on just a users own library. Imagine they are browsing all films, and want to filter out / in the films of ones they have already actioned (and perhaps genres / years / actors etc but i think that will be ok as its edges) You'll note my other post is about v

[orientdb] Graph queries- beginners tips please :)

2015-05-02 Thread Sky Viker-Rumsey
Hi I've finally got round to building a nodeJs web API using OrientDB, but I'm not just starting the stage of wanting to query the data but immediately struggling as I'm finding clear documentation hard to come by. I normally work best from examples where I can pick up on quickly. My model is

[orientdb] Fetch plan - strings quacking like RIDs

2015-01-06 Thread Sky Viker-Rumsey
Hey I just did a little test with my own data, and it seems if I create a string field on a vertex e.g. foo, and enter a value that looks like an @RID (and lets say for arguments sake it's valid), then using a fetchplan select against this vertex, then foo is populate with that record it was p

Re: [orientdb] Lightweight Edges vs Other Edges

2015-01-03 Thread Sky Viker-Rumsey
LWE work for me on something such as Genre categories for a film. However, when I want to update the film, which it's easiest for me to remove all edges first as there could be additions or subtractions to the genre / actors etc, I am struggling to write a SQL query that should simply do somet

[orientdb] Re: Design and SQL questions

2014-12-16 Thread Sky Viker-Rumsey
once you escalated the invitation to a vertex, give your queries more thought - the solution becomes relatively simple (albeit just requires learning the query language) In psuedo talk it's for all out connecting 'invitation' vertices ('sent' edge), find all players that 'was_sent' (edge) tha

[orientdb] Re: Design and SQL questions

2014-12-15 Thread Sky Viker-Rumsey
Hey I have something similar with 'Reocommendation' to support Gregs response. I decided that Recommendation is a vertex, with 3 edges (1 In, 2 outs). The 'In' is: User -> recommends -> Recommendation then the 2 Outs are Recommendation -> recommended -> Film Recommendation -> was_recommended_

[orientdb] ETL and In<->Out edge creation

2014-12-04 Thread Sky Viker-Rumsey
Hey Well not long since my last question which at least means I'm starting to work with OrientDB :) For learning I thought I would look at migrating some of my RDBMS data across. Importing the films and users no problem with ETL. However, I wanted to then import the edges for actions the user

[orientdb] Modelling a film recommendation

2014-12-04 Thread Sky Viker-Rumsey
Hi all, Im wanting to restructure my existing polyglot app which is a mix of MongoDB and Postgres, to using OrientDB. The reason is that I want to rewrite the site to allow for a more fluid social model with the follow / following and be able to infer connections. On top of that, given it's fil