Luigi,
It's been almost two months since we asked about this. We'll turn off the
strictSQL option if we have to, but that doesn't seem like a good long-term
solution. We really would like a way to do this.
We're having major memory issues with our current version of OrientDB, and
would like to
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 follow
> up as soon as I can.
>
>
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 pars
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 it
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 strictSQL=fal
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 feed
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, so that I can try it and giv
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 returns (looks like it g
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
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 givennam
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') (
give
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 y
Hello,
I'm using OrientDB 2.2.32. We're updating our software from 2.0.8.
The traverse() operator in selects does not appear to be working.
When I run the attached program, I get
a com.orientechnologies.orient.core.sql.OCommandSQLParsingException.
Exception in thread "main"
com.orientechnolo
13 matches
Mail list logo
