Re: [orientdb] readable query is slow, fast query is un-readable

2016-09-19 Thread Luca Garulli
Have you tried with: select expand(out().out('ohlc')) from ohlc where asset= #58:2 Best Regards, Luca Garulli Founder & CEO OrientDB LTD Want to share your opinion about OrientDB? Rate & review us at Gartner's Software Review

[orientdb] readable query is slow, fast query is un-readable

2016-09-19 Thread hartmut bischoff
Hi, in a previous mail, I attached a test-database with - a timegraph 'jahr', 'monat' 'tag' - a class 'bar' - edges with a property "asset" pointing to a record in a class 'contract' There is also some inherence : ohcl<- price <- midpoint, volatility and so on. The Idea is,

Re: [orientdb] Re: Convert baasbox's db in graph trought OrientDB Studio

2016-09-19 Thread Luigi Dell'Aquila
Hi Daniele, Maybe I'm wrong, but if I remember well BaasBox uses links, not edges to represent relationships. I don't know the exact domain, so I cannot give you a migration procedure, but I think you should write one to convert links to edges Thanks Luigi 2016-09-15 18:20 GMT+02:00 Ivan

[orientdb] Re: simple query ist mysterious

2016-09-19 Thread Oleksandr Gubchenko
I've done some tests and you are right, with you db there is some strange behaviour. But this query seems to work fine: select * from option where 30 = strike or: select * from contract where 30 = strike

[orientdb] Re: simple query ist mysterious

2016-09-19 Thread Oleksandr Gubchenko
I've also tried it on 2.2.7 with option being sub-class of contract. All works properly. Il giorno lunedì 19 settembre 2016 09:36:02 UTC+2, Oleksandr Gubchenko ha scritto: > > On 2.2.10 I get this: > > >

[orientdb] Re: simple query ist mysterious

2016-09-19 Thread Oleksandr Gubchenko
On 2.2.10 I get this: Your option class is a superclass of contract? Il giorno lunedì 19 settembre 2016 09:26:30 UTC+2, hartmut bischoff ha scritto: > > I'm using

[orientdb] Re: simple query ist mysterious

2016-09-19 Thread hartmut bischoff
I'm using 2.2.7 On Monday, September 19, 2016 at 8:42:38 AM UTC+2, Oleksandr Gubchenko wrote: > > I've tried it on the latest 2.2.10 and both studio and rest (using

[orientdb] Re: How to remove outdated edges while importing data through etl in Orientdb?

2016-09-19 Thread alessandrorota04
Hi, can you explain better what you do with your update ? In any case when you delete a vertex the edges coming in and out of vertex are deleted. Best regards, Alessandro -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from

[orientdb] Re: simple query ist mysterious

2016-09-19 Thread Oleksandr Gubchenko
I've tried it on the latest 2.2.10 and both studio and rest (using postman) give me the right result: {"result":[{"@type":"d","@rid":"#21:0","@version":1,"@class":"contract", "strike":30,"@fieldTypes":"strike=c"}]} Alex. Il giorno lunedì 19 settembre 2016 08:35:01 UTC+2, Oleksandr Gubchenko ha

[orientdb] Re: simple query ist mysterious

2016-09-19 Thread Oleksandr Gubchenko
Hi, which version are you using? Il giorno lunedì 19 settembre 2016 08:20:41 UTC+2, hartmut bischoff ha scritto: > > Hi, > > I was very surprised, that a simple query " select from something where a > = b " could be a subject. > > but > 2.3.1 :001 > DB.execute{ "select from contract where

[orientdb] simple query ist mysterious

2016-09-19 Thread hartmut bischoff
Hi, I was very surprised, that a simple query " select from something where a = b " could be a subject. but 2.3.1 :001 > DB.execute{ "select from contract where strike = 30" } => [] 2.3.1 :002 > DB.execute{ "select from contract where strike between 30 and 30" } => [#"d",