GraphQL "where" clause: filter using a "Text Field" I have used in all the Content Items

[MarGraz]

Hi everyone,

I already read a similar topic here, but my question is a bit different. I'm working on several headless Orchard Core 1.8.3 microservices, and I want to be able to query the different Content Items I created, using GraphQL with a where clause on a "UserId" Text field that all the Content Items I created have.

I followed the learning path about GraphQL, and here it explains how to implement a WhereInputObjectGraphType.

The problem is, I want to avoid defining n Models and n WhereInputObjectGraphType for each Content Item because the WhereInputObjectGraphType requires a model.

1. Is there a way to apply the where clause on a "UserId" Text field, across all the Content Items without defining n models?

2. Otherwise, do you think that the best way to achieve this is to create my custom SQL Query and use it through GraphQL?

3. Or is better to implement an ApiController and use the ISession? But I would lose the advantage of having GraphQL.

4. Perhaps I should use a Common part (*) to have only one model? I think that in this case the problem becomes filtering using the correct Type, because there isn't a ContentItemType in the where clause.

Thank you

(*) To add a Common part, go to the Content Type, add a part of type Common, and save. Now click on the 'Edit' button of the common part, then select 'Part Definition' (on the green banner), and click 'Add Field'. Choose a Text field to be used as a common part, and save. Add the same Common part to the other Content Types.

[MarGraz]

@Piedone do you have any idea of what could be the best solution? 😊

Thank you

[Piedone]

I don't think there's a built-in way to expose content fields in GraphQL for filtering automatically.

We could perhaps extend Content Fields Indexing (SQL) with this, since it allows you to filter on content fields from SQL queries. That can also be used in the Queries module, so another workaround would be to expose SQL Queries in GraphQL, what's not available now, only for Lucene and Elasticsearch queries.

[Piedone]

While I was referring to querying for this, unfortunately, this won't get you fully there with GraphQL, since this is only about SQL Queries. And the connection to GraphQL is missing, so that's what I think we should add: the easiest would perhaps be to expose all SQL Queries in GraphQL, exactly as what happens for Lucene and Elasticsearch Queries.

I should've actually linked here, since that's about the module. There it's quite clear that we're talking about a module (what, as all modules, need to be turned on). Somewhat confusingly, the rest of the page is about indexing in general. Perhaps that needs clarification.

[MarGraz]

Thank you for your reply.

the easiest would perhaps be to expose all SQL Queries in GraphQL, exactly as what happens for Lucene and Elasticsearch Queries.

But is not implemented yet in Orchard Core, if I understood well.

I should've actually linked here, since that's about the module.

Don't worry, I was focused on the bottom of the page and I didn't see the module paragraph 😅

In the end I think I will implement ApiController for all CRUD actions, probably is the fastest way to achieve my goal.

Thank you

[Piedone]

Yes, this needs to be added to OC. I opened an issue about it: #16008.

[MarGraz]

Thank you so much 😊

[Piedone]

No problem.