It seems the 2.1.1 query parser has gotten much stricter since 2.0.x releases as follows:
1. Query parser used to accept CREATE EDGE FROM x TO y or CREATE EDGE TO y FROM x in any order. Now orientdb forces you to put FROM first in all cases. 2. Query parser used to accept multiple limit statements (user error) and now only accepts one 3. Deleting vertices via a subquery is non-functional. https://github.com/orientechnologies/orientdb/issues/4523 Beware that you may need to refactor queries in your app to adapt. -- --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
