---
title: "Comment by Araxas on \"GraphQL vs REST: putting it to rest\" | Hashnode"
description: "Another article saying rest has no way to limit the data. There are tons of ways to do this, the API you are using as an example chose NOT to implement any. ODa"
url: "https://hashnode.com/posts/graphql-vs-rest-putting-it-to-rest/62b3010082c37c9011bf2b4c/comment/62bb54fdc2f205e7cdb18a81"
---

[Discussion](https://hashnode.com/posts/graphql-vs-rest-putting-it-to-rest/62b3010082c37c9011bf2b4c)

Comment [GraphQL vs REST: putting it to rest](https://hashnode.com/posts/graphql-vs-rest-putting-it-to-rest/62b3010082c37c9011bf2b4c)

[Araxas](https://hashnode.com/@Araxas)

[Jun 28, 2022](https://hashnode.com/posts/graphql-vs-rest-putting-it-to-rest/62b3010082c37c9011bf2b4c/comment/62bb54fdc2f205e7cdb18a81)

Another article saying rest has no way to limit the data. There are tons of ways to do this, the API you are using as an example chose NOT to implement any. OData had a way to limit data, even pass query params, join info, etc. This is not new.

GraphQL is not magic, someone still had to implement the API to do the query the right way, etc. You can do the same and expose a REST and GraphQL endpoint that do the same things.

[Lucky victory](https://hashnode.com/@codewithveek)

[Nov 26, 2022](https://hashnode.com/posts/graphql-vs-rest-putting-it-to-rest/62b3010082c37c9011bf2b4c/comment/62bb54fdc2f205e7cdb18a81#reply-6381dcc960dba100605a7ed6)

Yeah, you're right, In some of the APIs I have built (mostly for personal use), I do include a `fields` query param, which is a string of column names delimited by a comma, which I validate against my an array of database column names, this way I can return specific data.
