Order by multiple fields

[marktani]

{
  # order ascending by name first, then descending by birthday
  allUsers(orderBy: [name_ASC, birthday_DESC]) {
    id
  }
}

[dohomi]

very important.. would love to see this feature out of the backlog :)

[lucasfeliciano]

Yes! :)

[njreid]

Yes please!

[kbrandwijk]

Would be half a feature if it was limited to top level fields. I think the orderBy parameter Type should mirror the query Type, so all fields down the hierarchy are available for orderBy.

[jjwp]

@kbrandwijk half a feature is better than not having it at all. Would love to see this live, we currently have a use case for ordering by a category first, then a date field.

[renecvt]

Any news on this?

[LucaGabi]

Hi .. I also have an idea (just as an idea to be improved if considered..):


query{
  films{
    title[='st%'*='at%']
    +year[=1998*=2011..2013*>2016]
    +auth
    +cinemas|skip,take|{
        city|asc|[='bu%']
        +d=dist(#c,l)|desc|[<=700]}
  }
}



Where operator:  
* is 'or'  
+ is 'and'   
.. is 'between'  
... is 'open right range [..)'  
.... is 'open right range (..]'   
field[op value ...] is where field op value  i.e. age[>22]  
d is 'computed field' 
#c is a parameter  
field|skip,take| is paging on collection  
field|desc| is order desc  
[=val,...] equal sign can be implicit and omitted

[phunkren]

Can anyone give a status update on this please?

[PascalSenn]

I built a filter abstraction for graphql-dotnet, which is similar to prisma.
I did solve that issue with passing all filterable items to orderBy as own properties:

query{
  servers(
  orderBy: {
    active: DESC
    assetNumber: ASC
  }
  ) {
    id
    active
    assetNumber
  }
}

You can even specify the order of orderBy statements. The example above is first ordered by active and then by assetNumber. The following would be first ordered by assetNumber and then by active

...
  orderBy: {
    assetNumber: ASC
    active: DESC
  } 
...

That would also be a solution for #95

query{
  servers(
  orderBy: {
    active: DESC
    assetNumber: ASC
    customer: {
        name:ASC 
   }
  }
  ) {
    id
    active
    assetNumber
    customer {
         name
    }
  }
}

That probably would end up in breaking changes though.

[Yogu]

How do you specify the order (sequence) of the order clauses? Does graphql.net preserve the order of input fields? But even if it does, the client may have problems preserving the order of properties in a variable value. Otherwise, I'd go with an array of enums (the enums being prisma's current enum) - that's how we do it in cruddl.

[PascalSenn]

@Yogu it doesn't. Just tried.

[PascalSenn]

It does preserve the order. The problem was that I didn't handle OrderBy and ThenBy properly.
For my case it does work.

Json serializers should preserve the order.
At least JS (Chrome 65) does:

var serializationObjectBefore = {
	orderBy: {
        customer: "Test",
        active: "Test"
    }
}
var first = JSON.stringify(serializationObjectBefore) 
var serializationObjectAfter = JSON.parse(first) 
var second = JSON.stringify(serializationObjectAfter) 
var serializationObjectBefore =  JSON.parse(first) 
second
"{"orderBy":{"customer":"Test","active":"Test"}}"
first
"{"orderBy":{"customer":"Test","active":"Test"}}"

But still.
I'd rather use nested objects if you want to ensure compatibility:

orderBy: {
      assetNumber: {
            position: 1,
            direction: DESC
     }
}

[PascalSenn]

@Yogu

"GraphQL Objects represent a list of named fields, each of which yield a value of a specific type. Object values should be serialized as ordered maps, where the queried field names (or aliases) are the keys and the result of evaluating the field is the value, ordered by the order in which they appear in the query."

http://facebook.github.io/graphql/October2016/#sec-Objects

[dohomi]

@sorenbs thanks for the clarification I already had the feeling that there is nothing happen any longer in the graph.cool world. Sad for me I thought that it was an amazing idea and I have many production apps online.

[FluorescentHallucinogen]

@sorenbs

First of all - I'm sorry that we published a roadmap, and then failed to deliver on it in a timely manner and furthermore failed to communicate our lack of progress. We will do better in the future.

When the public roadmap will be eventually published (see #2142)?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

[zhiwenjunjin]

any update on this, nya?

[jvlobo]

any plans on implementing this feature? it seems like a very important one to have...

[jwld]

Would love to see this added 🙏

[oreillyross]

Yes me too, would love to have this feature built-in

[kumarabhirup]

I need this feature!

[MikeAliG]

+1

[bkstorm]

this issue was removed from ROADMAP.md 5 days ago :(

[iwasingh]

Would love to see orderBy by multiple fields and inner relations ordering

Any updates?

[mahapo]

+1

[esausilva]

This is a must have feature. I hope Prisma 2 can bring it to life 🙏

[tafelito]

@sorenbs none of you large customers had to implement something like this? It seems to be a pretty common use case

[Jaikant]

This is a much needed feature, even for hobby project!

[anaibol]

I switched to AWS AppSync

[charleslouis]

Hi,
This is indeed so much needed 🙏

[phryneas]

@charleslouis This will not be coming. Prisma 1 is dead.

[charleslouis]

@phryneas alright. Thanks for letting me know.

[beautimode]

+1

[deanshelton913]

+1