Add SQLAlchemyList and SQLAlchemy mutations types

[Toilal]

This brings default support for fields filtering and ordering on queries and mutations.

This is a work in progress for comments, please do not merge for now.

[coveralls]

Coverage decreased (-14.4%) to 76.389% when pulling a8f6718 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage decreased (-14.4%) to 76.389% when pulling a8f6718 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage decreased (-14.4%) to 76.389% when pulling a8f6718 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage decreased (-14.4%) to 76.389% when pulling 6945888 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage decreased (-14.4%) to 76.389% when pulling 6945888 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage decreased (-14.4%) to 76.389% when pulling ffc4d71 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage decreased (-14.4%) to 76.389% when pulling ffc4d71 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage decreased (-14.4%) to 76.389% when pulling ffc4d71 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage decreased (-14.5%) to 76.334% when pulling 365a0ec on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage decreased (-4.7%) to 86.079% when pulling 596a72b on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage increased (+0.1%) to 90.951% when pulling ae30f00 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage increased (+0.9%) to 91.667% when pulling 9936191 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage increased (+0.8%) to 91.579% when pulling f89fa11 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage increased (+1.2%) to 92.008% when pulling 894517d on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[coveralls]

Coverage increased (+1.2%) to 91.992% when pulling 919bbd6 on Toilal:filtering-and-relationships into ecd9a91 on graphql-python:master.

[Toilal]

There's only an update_all mutation missing I think now. Could you review this pull request ? Maybe it requires some documentation update too ?

[amilstead]

+1 Looking forward to this in a release so I can remove my copy-pasta of this diff in my own codebase.

[robjampar]

+1 yeah this looks really useful

[XiaoMouR]

Cool jobs!

----update----
A little question with the code as follows

class Tags(SQLAlchemyObjectType):
    class Meta:
        model = models.Tags  # a SQLAlchemy model that contains two columns (id,name)
        interfaces = (graphene.relay.Node, )

class UpdateTags(SQLAlchemyUpdate):
    class Meta:
        model = models.Tags
    Output = Tags

class Query(graphene.ObjectType):
    tags = SQLAlchemyConnectionField(Tags)

class Mutation(graphene.ObjectType):
    update_tags = UpdateTags.Field()

schema = graphene.Schema(query=Query, mutation=Mutation)

I get a tag with result {"id":"VGFnczox","name":"test"}, but the follows mutation won't success.

mutation{
  update_tags(id:"VGFnczox",name:"test2"){
    id
    name
  }
}

I track the excution and find that SQLAlchemyUpdate's mutate will accept id as VGFnczox instead of translate it to an integer, which causes UpdateTags failed.
So far, my testing has been limited to the GraphiQL console, so am I missing something?

[qubitron]

@Toilal re: relationships I've left some comments on #29 on how I've been handling them.

[Toilal]

I've actually abandonned trying to implement a GraphQL service with Python :(.

(switched back to REST and Spring/Kotlin)

[alexisrolland]

Bump, I'd love to see this implemented in graphene-sqlalchemy.
Thanks @Toilal for your contribution on this.

[flewellyn]

I can confirm that this works beautifully, and is precisely what I needed. How soon can this be merged?

[macic]

Hey, can this be merged, after resolving the conflict?

[kavink]

@Toilal Would it be possible to resolve the conflict also if possible would be great to update the README or the documentation with usage/example or some blurb about this feature, @syrusakbary Any idea who the maintainer of this repo is and if they can review and merge this PR ?

[lorcanoeire]

Great feature. How soon can the PR be merged?!

[arlobryer]

This would be very useful for us too - currently looking into how we generate mutates straight from SQLAlchemy model. Looks like this would do it 😀 .

[nayak16]

Any word from the authors about when this would be merged?

[syrusakbary]

I would take a look on this PR soon, sorry for the delay.

[qubitron]

@syrusakbary note that there's been quite a bit of improvements to these classes on #29, the latest versions are available as gists in that issue

[yoursdearboy]

Any updates?

[danaronson]

any updates?

[NJannasch]

Any updates?

[TeaDove]

Any updates?

[pgzmnk]

Any updates?

[palisadoes]

My organization has been using graphene-sqlalchemy-filter for filtering, however the repo has become inactive. Would anyone on this thread be interested in integrating the graphene-sqlalchemy-filter features into graphene-sqlalchemy as a sponsored activity?