Enum datatype (v1)

[Ignition]

Introduce the Enum datatype.

• Compact representation for a finite set of members
• Semantically more meaningful than ints
• More performant than string comparisons

Expected that if user has less than 256 named enums, each with less than 256 values, then their property store value representation will be 2 bytes for any enum value used. This will be better than string encoding, where "London" would be 7 bytes (1B size + 6 for the text).

Example commands

CREATE ENUM Location VALUES { York, Zagreb };
ALTER ENUM Location ADD London;
ALTER ENUM Location UPDATE VALUE London TO Westminster;
MATCH (n {city: Location::York}) RETURN n;

[Ignition]

Tracking

• Part of Epic [EPIC] Enum datatype #2042

Documentation checklist

• Add the documentation label tag
• Add the bug / feature label tag
• Add the milestone for which this feature is intended
• Write a release note, including added/changed clauses
  • Added new enum data type
• Link the documentation PR here
  • Enum datatype (v1) documentation#852
• Tag someone from docs team
  • @kgolubic

Extra work

• @MarkoBarisic Can you add https://github.com/rollbear/strong_type.git to our cache

[kgolubic]

@Ignition I'm missing the Release note entry and documentation PR.

Update: docs PR is memgraph/documentation#852

[sonarcloud]

Quality Gate passed

Issues
0 New issues
34 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
12.8% Duplication on New Code

See analysis details on SonarCloud

[kgolubic]

For Release note I'll use:

• The support for the Enum datatype has been added. Enums can be used to enhance query performance and reduce memory usage compared to string representations.
  #2039