graphback
graphback copied to clipboard
aerogear
Graphback - Out of the box GraphQL server and client
The only way to make a `@oneToOne` field truly 1:1 is by also adding `@unique`. ```graphql """@model""" type User { id: ID name: String """ @oneToOne @unique """ note: Note...
@wtrocki I'm opening this issue so we can continue the discussion around potentially integrating [Sqlmancer](https://github.com/danielrearden/sqlmancer) into Graphback. Adding Sqlmancer under the hood would potentially provide a lot of extra functionality...
Things have been going very well for me today! I've started to incorporate graphback into a large project to get rid of Prisma. One significant issue I am facing is...
## Problem This creates a `user.details_id` column in the database, and enables relation data fetching when querying the User model. ```gql @model type User { id: ID! """ @oneToOne key:...
## Overview Graphback gives capability to customise database column name during database generation with the `@db.name` annotation. See [Changing column names in graphback](https://graphback.dev/docs/database-schema-migrations#changing-column-names-in-graphback). Graphback does not offer a simple way...
When fetching single item I can paginate it's results but there is no pagination on relationships - fetching all of them effectively. The same problem - when fetching tasks we...
In looking through the documentation, I don't believe there is any significant mention of transactions for queries and mutations. Transactions will be very important to support, since they open up...
It would be nice to have a unique annotation. It could possibly enforce unique constraints, but also it could open up the `get` query to allow querying by fields besides...
## Templates should have separation of concerns When using Graphback templates we geting index.ts file that has multiple elements and concerns that developers need to read. It will be much...
I have a join table that does not have a primary key in my database. Graphback requires one, so I put the field in the schema. This works, and I...