Q: Joins, query parameters?
If these features are not supported—filtering, pagination, or table joins—it raises concerns about the scalability and production readiness of the service. Could you clarify how your platform handles these use cases or recommend best practices for managing such limitations?
jass_
Jan 12, 2025A: Hi,
Filtering is supported. You get a dedicated endpoint just to fetch results based on filters you pass.
JOINS: This is in development and will be launched soon. We know the importance of it and understand how it can be critical in fetching combined results.
PAGINATION: This is something we will be working on once we build out JOINS.
Thanks
Riya_NoCodeBackendHey chris-james
Just wanted to share an update that creating JOINS is now possible inside NoCodeBackend. You can check this video for more info: https://www.youtube.com/watch?v=t2Zps53hn9U
chris-jamesThat’s awesome. Thanks for the quick reply and it looks like you guys are turning out new features really fast that’s great
I would like to suggest making a new API endpoint per join because a user might still need to just get the courses data as well. so maybe course_students should be the join end point.
handmedown
Verified purchaser
Hi there,
Thanks a lot for launching this. I had a doubt. In the above comment you've mentioned "You get a dedicated endpoint just to fetch results based on filters you pass". What is the format to pass these filters? I couldn't find any documentation or inputs in the API documentation to pass these.
Hi,
It's there in the API documentation itself. The filters are nothing but the column values you pass.