Jason Athanasoglou

Hey Ansis, thanks for your message. This kind of uniqueness can be achieved on a neo4j-level, since Neogma can't go anything for it. For example, will a [unique index](https://neo4j.com/docs/cypher-manual/current/constraints/examples/#administration-constraints-unique-nodes) fit...

Hey there, There is no way in Neogma to do this, and the answer in your link can be easily created using Neogma's `QueryBuilder`! Adding it as a Model static...

Correct. This cannot be built by using only build-in operators, but it can be built by using `raw`. For example: ```ts .merge(...) .raw(`ON CREATE SET keanu.created = timestamp()`) .return([...]); ```

Thanks for the suggestion and all this information. This is something I have considered, but skipped due to time limitations (mostly because of the typings). In my app, I just...

This is something that I definitely want Neogma to be capable of doing, as it will be very useful! Since I've been using `QueryBuilder.match.related` a lot in my application: 1....

> Does anyone have any workaround for now? Do we need to use query builder for removing relationships? > > Edit: Also, is there any specific reason this wasn't implemented...

It's finally here! Deployed in version [1.11.0](https://github.com/themetalfleece/neogma/releases/tag/v1.11.0). I've also added various workflows to allow easier contribution to neogma, which are all described in the releate notes.

Hey! Yeah, I've also been thinking about it lately. This could be the next thing I look into. After using sequelize a lot, I'd prefer if all indexes are declared...

In the beginning I was using `class-validator`, but it was complicating things a lot (i.e. I had to befine the class anyway, then pass it to `ModelFactory`). So I ended...

Thanks for all that info! It'll come in handy when I consider replacing revalidator