OrientDB 3.0.0RC1 and this Manual are still in development. Not suitable for production environments.

Upgrading to OrientDB 3.0

General information

Developing OrientDB 3.0 we put a lot of attention on maintaining backward compatibility with v 2.2. In some cases though, we had to do some small breaking changes to make the whole solution more consistent.

Here is a list of the things you should know when migrating to v 3.0

Schema

Case sensitive property names

In v 2.2 property names are case sensitive while working schemaless, while if you work schemaful property names are treated as case insensitive.

Eg. consider the following queries:

Query 1:
SELECT name from V

Query 2:
SELECT Name from V

In v 2.2:

  • Query 1 and Query 2 are equivalent if you are working schemaless
  • Query 1 and Query 2 are different if you declared name property in the schema for V

In v 3.0 these two queries are always different, so Name and name are considered two different properties (with or without a schema)

When migrating from v 2.2 to v 3.0, review your queries and make sure that you are writing property names in the right case

Note: CLASS names are still case insensitive

Case sensitive index names

In v 2.2 index names are case insensitive

In v 3.0 index names are case sensitive

When migrating from v 2.2 to v 3.0, review your queries and make sure that you are writing index names in the right case

SQL

See full SQL reference

UPDATE ADD/PUT/INCREMENT

In v 2.2 there was a specific syntax for:

  • adding values to lists: UPDATE AClass ADD aListProperty = "a value to add"
  • adding elements to maps: UPDATE AClass PUT aMapProperty = "a key to add", "a value to add"
  • incrementing values: UPDATE AClass INCREMENT aNumberProperty = <aNumber>

This syntax is limitating, misleading and hard to read, so we decided to switch to a more natural syntax, as follows:

UPDATE ADD:

V 3.0 has a new || operator that allows to concatenate lists and sets:

UPDATE AClass ADD aListProperty = "a value to add"

becomes

UPDATE AClass SET aListProperty =  aListProperty || "a value to add"

but it can also be used to concatenate the value on the left:

UPDATE AClass SET aListProperty =  "a value to add" || aListProperty

or to concatenate multiple values:

UPDATE AClass SET aListProperty =  aListProperty || ["a value to add", "another value"]

UPDATE PUT:

The UPDATE PUT syntax is actually redundant, even in v 2.2. It can be replaced with dot notation or with square bracket notation:

UPDATE AClass PUT aMapProperty = "a key to add", "a value to add"

can be written as:

UPDATE AClass SET aMapProperty["a key to add"] = "a value to add"

or

UPDATE AClass SET aMapProperty.`a key to add` = "a value to add"

UPDATE INCREMENT

The INCREMENT syntax is limited to adding numbers to numbers. In v 3.0 we removed this option and replaced it with a much more flexible set of operators:

+=  // add and set
-=  // subtract and set
*=  // multiply and set
/=  // divide and set
...

The following:

UPDATE AClass INCREMENT aNumberProperty = 15

can be written as

UPDATE AClass SET aNumberProperty += 15

that is equivalent to

UPDATE AClass SET aNumberProperty = aNumberProperty + 15

But also the following are valid

UPDATE AClass SET aNumberProperty -= 15

equivalent to

UPDATE AClass SET aNumberProperty = aNumberProperty - 15

and so on so forth

eval() function

V 2.2 did not support expressions in SQL projections and filters, so you had to use eval() function to explicitly calculate them.

V 3.0 has full support for expressions in SQL, so you can re-write your queries removing the eval() function, eg.

SELECT eval(' age + 10 ') as ageInTenYears FROM Person

can be written as follows in v 3.0

SELECT age + 10 as ageInTenYears FROM Person

The same applies to WHERE conditions, eg. the following query is valid in v 3.0

SELECT FROM Person WHERE age + 10 < 50

FETCH PLAN

In v 3.0 FETCH PLAN is deprecated, and no longer works in most of the scenarios. It was replaced by a much more flexible syntax: nested projections

See full syntax here

Other changes in SQL

See SQL changes

Release notes

General information on how to upgrade OrientDB can be found in the Upgrade Chapter.

You may also be interested in checking the Release Notes.

results matching ""

    No results matching ""