Order by related fields

[marktani]

Example: a User has many Posts. Should be possible to order the Posts by User name.

Maybe:

query {
  allPosts(orderByRelated: [user_name_ASC]) {
    id
  }
}

[cameronk]

This would be a lifesaver!

[edtsech]

@marktani any workaround we can use for the time being?

[marktani]

The best workaround I'm aware of, is to order items client side 🙂

[shanecav]

It would be great to be able to order by "to-many" related fields as well (by the count of related items).

For example, to get a list of the top 10 most voted-for links (assuming votes is a related field of type [Vote!]!):

query {
  allLinks(first: 10, orderBy: votes_DESC) {
    id
    url
    description
    _votesMeta {
      count
    }
  }
}

Currently, to get that list you'd have to query for every Link and then sort/slice it on the client, which is potentially a ton of overfetching.

[kenyk7]

A question for when they plan to add this improvement?

[studentIvan]

+1 for this

[jeromeky]

+1

[danstepanov]

+1

[serverlesspolska]

I see a lot of 👍
Dear GraphCool when do you plan to implement that?

[martinsura]

Must-have feature!

[danrasmuson]

In my case this table will have thousands of rows. My users won't be able to sort the table by "createdBy" or "dataset" until this feature lands.

[studentIvan]

@danielrasmuson you can create some sortable index just as temporary solution :)

[PascalSenn]

Have a look at #62
This would solve the issues:

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

[harrisrobin]

+1

[iyeremuk]

+1

[craigcbrunner]

Please add this and order by multiple fields!

[darthmolly]

+1

[nk1tz]

+1
I have a need for exactly this.
:)

[aandriamanga]

+1 💯

[terion-name]

VERY needed

[kumarabhirup]

is it yet not built???? how do I order my posts by number of upvotes???

[impowski]

Would be an amazing feature

[fenos]

Any update on this?

[bkstorm]

it's a really important feature. This issue was created two years ago and hasn't been fixed.

[valentinbe]

Definitely agree, we are patiently waiting for this feature to push Prisma to production here :)

[juliosampaio]

Any update on this?

[jvlobo]

Any update on this??? :(

[steebchen]

Can people please stop spamming this thread with "UPDATES????" and instead upvote the first comment? I does not help anything, they are currently working on Prisma 2 (where this feature will be integrated) and that will take a while. In the meantime, you're just notifiying 35 participants with no new information and thus wasting their time. I think they will update us once this feature is implemented.

[jvlobo]

Can people please stop spamming this thread with "UPDATES????" and instead upvote the first comment? I does not help anything, they are currently working on Prisma 2 (where this feature will be integrated) and that will take a while. In the meantime, you're just notifiying 35 participants with no new information and thus wasting their time. I think they will update us once this feature is implemented.

I upvoted the first comment months ago.
I guess people wouldn't "spam" if the Prisma team was a little bit more communicative, don't you think?

[iwasingh]

Another workaround to avoid ordering client-side is to put an index attribute on the model related to another field

type Vendor {
 id: ID!
 name: String
} 

type Product {
  _vendor_name: String
 vendor: Vendor
}

You have to handle _vendor_name updates manually but then you can

query {
  products(orderBy: _vendor_name_ASC) {  
   id 
   name
   vendor {
     name
    } 
  }
}

Yeah it's cumbersome, but works fine

If you want ordering by multiple fields then do it client side, it's the only solution

[bkstorm]

Or write a raw query, then use prisma.$fragment to get the type of data you need.

[juliosampaio]

@bkstorm could you provide us an example please?

[alan345]

Is this feature will never be launched?

[cesarve77]

it is a must to have feature, waiting almost 3 years?

[alan345]

Prisma team, Are you working on this feature for Prisma V2?

[homerjam]

Or write a raw query, then use prisma.$fragment to get the type of data you need.

@bkstorm Do you have an example of this please?

[bkstorm]

Or write a raw query, then use prisma.$fragment to get the type of data you need.

@bkstorm Do you have an example of this please?

I don't use Prisma 1 any more due to it lacks a lot of features, like this one, but I will try to create an example code for you.

[AdamErwee]

Or write a raw query, then use prisma.$fragment to get the type of data you need.

@bkstorm Do you have an example of this please?

I don't use Prisma 1 any more due to it lacks a lot of features, like this one, but I will try to create an example code for you.

Sorry, was just wondering if you ever got around an example for this?