Luca Steeb
Luca Steeb
The equivalent of https://www.prisma.io/docs/concepts/components/prisma-client/aggregations in Go.
Right now the syntax is `.FindOne(...).Update(...)` While that results in one efficient query under the hood, it may not look like it. To make this more obvious, we could revert...
The following results in a un-readiness error after a few seconds, instead of pretty-printing this error and immediately exiting: ``` {"is_panic":false,"message":"\u001b[1;91merror\u001b[0m: \u001b[1mEnvironment variable not found: DATABASE_URL.\u001b[0m\n \u001b[1;94m-->\u001b[0m \u001b[4mschema.prisma:10\u001b[0m\n\u001b[1;94m | \u001b[0m\n\u001b[1;94m...
When calling `Connect`, the command may succeed even though the database doesn't exist. Instead, I believe we could already error here and let the user know the database needs to...
``` _, err := s.prisma.Deploy.CreateOne( prisma.Deploy.ID.Set(id.Generate()), prisma.Deploy.GithubID.Set(strconv.Itoa(int(data.Event.CheckID))), prisma.Deploy.Hash.Set(data.Hash), prisma.Deploy.Branch.Set(data.Branch), prisma.Deploy.Project.Link( prisma.Project.Repository.Where( prisma.Repository.GithubID.Equals(data.Event.RepositoryID), ), ), ).Exec(ctx) ``` This is currently allowed syntax, but only a project ID can be linked –...
It looks like when no connection string is provided, the `Connect` call silently succeeds. This needs investigation first.
When the Prisma schema is not in the root, sqlite paths can't be resolved.
There should a few examples ready to install with different use-cases for the Go client.