DQL and GQL schemas are not in sync

Users
1

Hi,
I’m trying to build a schema using the GQL schema definition but I discovered that the @facets are still not supported.
Overcoming my disappointment I went into the DQL schema definition trying to do my best to complete the task of defining a minimal schema for my relations.
Here I discovered 2 major problems that are preventing me to go on:

  1. the schema definition in DQL is shipping also old definitions, the database is empty but the old definitions are still there even if I deleted all an recreated the schema.
    Example: here you could see the Actual.pointed_by and Actual.pointedBy which are boot coming from a very early stage of my schema definition. How this could be possible? Is this intentional?
...
Actual.config: string @index(fulltext, trigram) .
Actual.pointedBy: [uid] .
Actual.pointed_by: [uid] .
Group.contains: [uid] .
...
  1. Then I decided to use pure DQL to overcome synch and limitations but I’m noticing that even if the Query manual for DQL is quite rich (but doesn’t looks like a formal manual and this is slowing down our training phase) I haven’t been able to find how to define the facets for an edge which is one of the most important features of any GraphDB.

Could someone help?

2

Hey @Carlo_Cancellieri,

  1. Did you curl -X POST localhost:8080/alter -d '{"drop_all": true}'? That should definitely remove both the schema and predicates.
  2. Facets in Dgraph are not defined in the schema
3

I understand, I’m sorry I didn’t find this sentence in the documentation, I might have lost it.

4

You’re right. This fact is not articulated anywhere in the docs.

It could be because Dgraph started off as schema-less. In fact it still is, it will accept any subject-predicate-value (and optional facet) update over the wire and store it.