[FEATURE]: DQL Check Constraint

[jdgamble555]

Have you tried Dgraph before this proposal? and did not find anything similar?

No response

What you wanted to do.

It would be nice to have basic check constraints in DQL.

type Film {
  name
  release_date
  revenue @check(revenue > 1)
  running_time @check(running_time > 2.0)
  starring(starr
  director
}

SQL has a simple money example.

You could also add it as a top-level directive.

type Persons @check(age >=18 AND City='Sandnes') (
    LastName
    FirstName
    Age
    City
);

regex

type User {
  email @check(email ~* '^[A-Za-z0-9._+%-]+@[A-Za-z0-9.-]+[.][A-Za-z]+$'))
  username @notnull @check(length(username) >= 10);
  ...
}

This would require some basic string functions for matching, and would allow AND, OR etc...

What you actually did.

I would say regex and string functions would come later, but basic checks for greater than, equal to, etc should work initially. This would also have to translate a level up to GraphQL.

Why wasn't it great, with examples.

We can put anything anywhere. This is great sometimes, but other times we want constraints.

Additional information.

This could open up the door for type constraints as well. This would be optional of course. Could come down the line.

[github-actions]

This issue has been stale for 60 days and will be closed automatically in 7 days. Comment to keep it open.