Very cool, I’d appreciate if you bumped the thread if/when you add support for deleting the data. I’ve always found the process of deleting a node and all its edges to be the most frustrating part, so I’d be curious to see how you would handle it (:
I used this library the last days for getting a mysql database converted to dgraph and it helped me a lot.
For rapid devolpment of a new project, it would be cool if dgman would able to mutate the schema, maybe with another function or a non-default option to do so. If you come from a sql world like me, creating relations like 1:n, n:n in dgraph have mutliple ways to do it . So designing the data model I often changed just the index option like term/hash or adding @reverse.
Another thing related to the data modeling: Having a lot of tables to convert and getting errors back in some cases with no mention to the source (eg protocol errors), I ended up with doing CreateSchema for every node type extended with info about it.
Despite of this small isues, Dgman was easy to use for me and I think it’s a good start up tool for getting a new project to run, thank you
@tlmichael Thanks! yes, deleting is quite cumbersome, still figuring out how to make it simple.
@AugustHell Thanks! Great to know this library is of help.
Yeah, we thought of adding for updating the schema, the first doubt was for indexes, an update would require reindexing, we had troubles with those before. Maybe, when there is little data it would not be a problem. We’ll add it probably.
Can you share what protocol errors did you get? Thanks.
Just released v0.4.1 that supports updating schema index with the MutateSchema function. We added a workaround for the above protocol errors by parsing field with Struct types to uid, just a fallback though, as you said with 1:1 relations, I agree that it is not supported.