Enda

IIRC that flag does not work. https://github.com/aerogear/graphback/issues/1043 not sure why we closed this

I tend to agree also - this would mean deviating from the [GraphQL CRUD](https://graphqlcrud.org/) spec somewhat. Should we also propose it gets updated with this?

Although we generate `@manyToOne` fields/annotations from `@oneToMany` annotations, we don't support the inverse (yet). This is why ManyToOne is not documented as an option in https://graphback.dev/docs/intro/datamodel#relationships - though I can...

@wtrocki @machi1990 are we looking to get this in before or after 0.14.0?

**Example Schema** ```gql """ @db.name: 'user_account' """ type User { id: ID! """ @db.name: 'user_name' """ name: String age: Int } ``` ## Knex Level - Keeps database specific field...

We have decided to go with a Knex Level Implementation. - Builds a mapping definition on server start, keeping the mapping up-to-date with the latest generated schema. - Can map...

> To clarify. > Would we use this mapping on knex level or in crud methods? Knex level.

I'm going to take this one now - it's a crucial part of making Graphback work with existing databases.

On second thought I am going to hold off. https://github.com/aerogear/graphback/pull/916 will mean that how we map will change anyway so it would have to be rewritten.

Is this still an issue?