sqlmancer
sqlmancer copied to clipboard
danielrearden
Conjure SQL from GraphQL queries 🧙🔮✨
I'm running into an issue with the `orderBy` statement on a query. Fairly certain this is a bug with the type definitions since the code works correctly and is cribbed...
According to npmjs. Switching packages involves some migration tasks. [Details here](https://www.graphql-tools.com/docs/migration-from-toolkit/).
There's a number of naming conventions that could potentially be made configurable: - Argument names like `where`, `orderBy`, `limit` and `offset` - Logical operator field names like `and`, `or` and...
Sqlmancer should provide a way to enforce maximum values when calling the `limit` method, as well as a default limit value that could be set if the method is never...
The `@sqlmancer` directive could accept a list configuration objects instead of just one, allowing the generation of multiple database clients. This would be useful for projects that utilize more than...
The library currently makes use of schema directives for both transforming the schema and providing metadata about the underlying database. This works well enough, but will make it difficult to...
Hi! I'm interested in exploring and discussing what it'd take to implement the `Node` interface (and with that globally unique IDs) in Sqlmancer. This + connection based pagination would ultimately...
Sqlmancer looks great, but one missing functionality that would prevent me from adopting it is the lack of [relay-compatible connection definition and pagination](https://relay.dev/graphql/connections.htm). Unless I am missing something in the...
Following 'Getting Started' documentation, I'm getting error ``` (node:868) UnhandledPromiseRejectionWarning: Error: Unknown argument "dialect" on directive "@sqlmancer". Unknown argument "table" on directive "@model". Unknown argument "pk" on directive "@model". ```...
