You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a follow-up to a discussion on the Discord server.
Currently, ArcadeDB doesn't have support to define constraints on properties other than their type.
The only property setting currently implemented is default, which works nice but isn't properly documented in the manual from what I can tell.
Now that the project is pretty mature, users would benefit a lot if the constraints defined here were implemented:
…rties constrants
Implemented issue #481.
Now property can have the following constraints:
- mandatory (the property must be present)
- readonly (the property cannot be changed after the creation of the record)
- min (minimum value)
- max (maximum value)
- regexp (Regular Expression)
Hi,
This issue is a follow-up to a discussion on the Discord server.
Currently, ArcadeDB doesn't have support to define constraints on properties other than their type.
The only property setting currently implemented is
default
, which works nice but isn't properly documented in the manual from what I can tell.Now that the project is pretty mature, users would benefit a lot if the constraints defined here were implemented:
arcadedb/engine/src/main/java/com/arcadedb/query/sql/parser/CreatePropertyAttributeStatement.java
Lines 79 to 107 in 351583f
This would also bring the project closer to feature parity with OrientDB.
The text was updated successfully, but these errors were encountered: