Hi,
I've attached the database export, including the defined index. And here's
the query:
SELECT @rid FROM User WHERE state=active AND birthdayYear = 1994 AND
birthdayYear = 1958 AND ageMin = 59 AND ageMax = 59 AND height = 176
AND height = 161 AND heightMin = 188 AND heightMax = 188 AND
Well, with either approach you're actually using the Graph API once you
start using the OrientGraph object.
A Vertex (OrientVertex) is built on top of a document, and its ODocument
can be obtained by calling vertex.getRecord().
But an ODocument is not a Vertex.
By working with OrientVertex
Luca,
So I'll try and give you a full test case early next week. But basically
what I'm having trouble with is that its fine to put a index on the sub
query and that will make that part faster. But if the sub query were to
return 3000 rows the outer part of the query (where foo = bar) will never
Hi Jamie,
To speed up the query like:
select from (select expand(in()) from User where status = 'active')
where foo = bar LIMIT 10
You should have an index on User.status to avoid scanning all User. Can you
elaborate more the query that is slow?
Lvc@
On 5 March 2015 at 22:28, Jamie Blair
Awesome! I'm happy to see so many options now. Back when I had this
problem, couldn't find much of a solution. Glad that users will now have
multiple options where to start from when using ODB with Docker.
@Tobie thank you for your image. Haven't tried yet, but looks solid.
On Thu, Mar 5, 2015
Relative newbie Currently testing/building Analytical app with
OrientDB. Really like it al lot!
One thing that i cant figure out is the best way to import (historical)
google analytics data on a daily base.
Is the use of indexes the way to go? Or do i create Vertex for every
adwords
Actually the better approach for me is to stick with the document api and
do like so:
ODatabaseDocumentTx db = pool.acquire();
OrientGraph g = new OrientGraph(db);
Out of interest is the a way to cast ODocument to Vertex and vice versa?
PS Would be nice if you could provide a one liner in
I am getting this error too. Any progress on this issue? My application is
running OrientDB 2.0.4
Jing
--
---
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
Ok here is an example:
CREATE DATABASE remote:localhost/testdb root root memory
CREATE CLASS Data EXTENDS V;
CREATE PROPERTY Data.id INTEGER;
CREATE CLASS Tag EXTENDS V;
CREATE PROPERTY Tag.name STRING;
CREATE CLASS hasTag EXTENDS E;
CREATE VERTEX Data SET id = 1;
CREATE VERTEX Data SET id =
Hi everyone,
while playing around with OrientDB 2.0.4 I encountered the following
problem:
I have the following (schematic) classes
public class ClassA{
private String someData;
private ClassB embeddedClass;
}
public class ClassB implements Serializable{
private Integer
Hi,
A small sample database and the query you execute will be enough
Thanks
Luigi
2015-03-05 21:18 GMT+01:00 Máté Gábri gabrim...@gmail.com:
Hi Luigi,
sorry I'm new to this so please forgive my noob question. What should I
provide so that you can test it? My code (nodejs) I'm using for
11 matches
Mail list logo