# Database, Collections, State Variables, and Fetch: Verification and Suggestions

**URL:** <https://community.weweb.io/t/database-collections-state-variables-and-fetch-verification-and-suggestions/17055>\
**Category:** Ask us anything\
**Tags:** workflows, filter, supabase, weweb\
**Created:** [March 8, 2025, 4:53am UTC](https://community.weweb.io/t/database-collections-state-variables-and-fetch-verification-and-suggestions/17055 "2025-03-08T04:53:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![joaosander](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joaosander/32/12584_2.png) [@joaosander](https://community.weweb.io/u/joaosander)\
**Post date:** [March 8, 2025, 4:53am UTC](https://community.weweb.io/t/database-collections-state-variables-and-fetch-verification-and-suggestions/17055/1 "2025-03-08T04:53:22Z")

</div>

After some research (and a bit of a headache), I came across some interesting points related to what I was looking for in the post below. I also have some suggestions and would like to check if they make sense and if they could potentially be implemented in the future.

> [@Best practices for using Collections vs Requests+variable?](https://community.weweb.io/t/best-practices-for-using-collections-vs-requests-variable/4028/12):
>
> Hi @elyseholladay ! If I understand your question, I also went through this recently. Generally, those who came from Bubble have a little difficulty, because when we create an API call, we define whether it is an action call or a data call. In WeWeb/Xano there is no such distinction and “everything is exposed” to us. Currently I have to create all GET calls in Collections and POST and PATCH calls as a workflow, creating the parameters and linking them with the necessary parameters of the call…

Currently, the only way to update a collection is by refetching it entirely. If you need a partial update, you must store the updated data in a variable. - (is it still the same?)

My suggestion if makes sense \> Additionally, collections automatically generate a mirror variable, which can be used as a state variable. This eliminates the need to create one separately and serves as the ideal place to store updated data, as mentioned earlier.

A valuable enhancement would be the ability to clear a collection through a workflow.

Another key limitation is the inability to perform partial updates on collections, which would be highly beneficial.

My suggestion if makes sense \> The ability to fetch only the necessary data using filters in workflows would greatly improve efficiency.

---

<div class="post-metadata">

**Author:** ![DanielL](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/daniell/32/13398_2.png) [@DanielL](https://community.weweb.io/u/DanielL)\
**Post date:** [March 8, 2025, 6:06am UTC](https://community.weweb.io/t/database-collections-state-variables-and-fetch-verification-and-suggestions/17055/2 "2025-03-08T06:06:41Z")

</div>

Hi @joaosander, have you checked the update collection action? [Update collection | WeWeb Documentation](https://docs.weweb.io/workflows/actions/update-collection.html)