@wildan2711 my thoughts exactly. I had just finished implementing a generic approach to unique checking in my application when I stumbled upon the @id directive and related feature issue. I was excited I might get to rip out some code before I realized it was GraphQL only. That lead to me digging through the docs for a few hours before finally posting here.
There really are just a couple of features missing before Dgraph would be the clear default database for every kind of project, at least any project I’m likely to work on. You can see another of my posts for context: Graph Design, Foreign Keys, uid/[uid], and Correctness
For me, the list is actually pretty short, but would include:
- unique constraints
- enforce one-to-many relationships, ideally through explicit (and named) reverse relationships that support additions from the parent OR child node (reference).
Other types of generic constraints would also be nice, but aren’t quite as fundamental to keeping the proper shape of your data.