Hey @LJRB, this isn't something you need to implement yourself, we have the `@timestamp` directive for that! https://neo4j.com/docs/graphql-manual/current/type-definitions/autogeneration/#type-definitions-autogeneration-timestamp
You need to change your thinking here - if you don't want anything at all to be created if a user doesn't exist, you want to be updating that user as the root operation, and then performing a nested create of the comment. If the user does not exist, ...
Hey @Mreda, this is working as intended and when implemented was somewhat of a security decision to not report which data already exists in the database to frontend clients. However, this behaviour could be reviewed, so I've raised a feature request ...
Hey @Mreda, tricky problem you have here!
As a general rule, most directives cannot be combined with the `@relationship` directive as it stands.
You can achieve some of what you want using an `@auth` directive on the `Event` type itself.
created...
Hi @RichardBonnett, I'm afraid this is just an unsupported feature at the moment.
Feel free to raise a feature request at https://github.com/neo4j/graphql/issues/new/choose so we can keep track of this.
Thanks!
