Re: [orientdb] Select from where traverse operator not working

Luigi, When is the release of 3.0.0 planned? We're still waiting to hear back from you on how to do this. Thanks, Steve On Mon, Mar 26, 2018, 8:45 AM Luigi Dell'Aquila wrote: > Hi Steve, > > Sorry, we are pretty busy with the release of v 3.0.0, I'll try to

Re: [orientdb] Select from where traverse operator not working

Hi Steve, Sorry, we are pretty busy with the release of v 3.0.0, I'll try to follow up as soon as I can. The traverse() executor is still there, but only in the old SQL executor. The new parser (strict SQL) was implemented for the new executor, so it doesn't make much sense to have it in the

Re: [orientdb] Select from where traverse operator not working

Luigi, I haven't heard back on this. Since the backend to the traverse() is still there, we're wondering how much trouble it would be to add it into the new parser. It definitely has some powerful and unique use cases. If these aren't covered by the new match projection, I would suggest that

Re: [orientdb] Select from where traverse operator not working

Thanks so much! Steve On Tue, Mar 20, 2018 at 9:34 AM, Luigi Dell'Aquila < luigi.dellaqu...@gmail.com> wrote: > Hi Steve, > > Thank you very much, I'll check it asap. > There is a way to re-enable the old traverse, you have to disable strict > SQL parsing: > > ALTER DATABASE CUSTOM

Re: [orientdb] Select from where traverse operator not working

Hi Steve, Thank you very much, I'll check it asap. There is a way to re-enable the old traverse, you have to disable strict SQL parsing: ALTER DATABASE CUSTOM strictSQL=false Anyway, I wouldn't recommend it in the long run, as you will lose a lot of stability in SQL parsing I'll give you a

Re: [orientdb] Select from where traverse operator not working

I attached the java program that creates it to my initial report. On Tue, Mar 13, 2018, 9:08 AM Luigi Dell'Aquila wrote: > Hi Steve, > > ah, got it, the old traverse() stopped when it found duplicates, while the > MATCH doesn't. > > Do you have a dataset I can check,

Re: [orientdb] Select from where traverse operator not working

Hi Steve, ah, got it, the old traverse() stopped when it found duplicates, while the MATCH doesn't. Do you have a dataset I can check, so that I can try it and give you better help? Thanks Luigi 2018-03-13 16:03 GMT+01:00 Steven Tomer : > Luigi, > > That query never

Re: [orientdb] Select from where traverse operator not working

Luigi, That query never returns (looks like it goes into an infinite loop). I had to kill the server process to make it stop. Any other ideas? Steve On Tue, Mar 13, 2018 at 8:16 AM, Luigi Dell'Aquila < luigi.dellaqu...@gmail.com> wrote: > Hi Steve, > > Try this > > SELECT expand(person) FROM

Re: [orientdb] Select from where traverse operator not working

Hi Steve, Try this SELECT expand(person) FROM ( MATCH {class: Person, as: person, where: (givenname = 'William')}.in(){while: ($depth = 0 OR givenname != 'George'), where: (givenname = 'George')} RETURN person ) The $depth = 0 guarantees that you don't stop traversing immediately; the

Re: [orientdb] Select from where traverse operator not working

Hello Luigi, That's sad news indeed. It will require a major task to rip out all of the places we're using traverse(). I've been playing around with the MATCH operator, and I can't get it to model the former query: SELECT FROM Person WHERE givenname = 'William' and in traverse(0,-1,'in') (

Re: [orientdb] Select from where traverse operator not working

Hi Steven, The traverse() operator was deprecated long time ago and is not fully supported anymore. I strongly suggest you to use TRAVERSE queries ( https://orientdb.com/docs/2.2.x/SQL-Traverse.html) or even better MATCH queries (https://orientdb.com/docs/2.2.x/SQL-Match.html) Another thing: if