# Weird things in the weweb data object for my supabase collection

**URL:** <https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096>\
**Category:** Ask us anything\
**Created:** [June 17, 2023, 1:05pm UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096 "2023-06-17T13:05:54Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaredgibb](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@jaredgibb](https://community.weweb.io/u/jaredgibb)\
**Post date:** [June 17, 2023, 1:05pm UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096/1 "2023-06-17T13:05:54Z")

</div>

i am setting up a collection from supabase  
i have set a limit of 25  
my DB has 450 records total that satisfy the query  
my query returns all 450 records  
when i access the query.data array, there are a BUNCH of null object. 425 in fact. then 25 objects of data at the end of the array.

the only way I can limit or paginate successfully with supabase is by making the API calls myself as shown here.

> [@How do i correctly use the paginator element AND can i use custom elements to achieve the same effect](https://community.weweb.io/t/is-there-a-way-to-grab-page-2-of-a-collection-from-supabase/3089/7):
>
> Can you tell me more about how this works with a collection from supabase. It’s not like xano where you can simply send a pagination variable. what you are suggesting only mimics pagination. instead what you are suggesting actually simply increases the limit and brings in more records which only slows down my query. that would be handy if i wanted a ‘see more’ feature but that’s not what i’m going for. instead i want to only get the first 25 records, then the next 25 and so on. @Joyce hopefu…

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [June 17, 2023, 3:33pm UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096/2 "2023-06-17T15:33:59Z")

</div>

Hey Jared,

Ok this is weird indeed. Can you open a bug ticket [here](https://support.weweb.io/)?

Just reported it to the team as well but if you open a ticket, you’ll be able to track its progress in real time 🙂

---

<div class="post-metadata">

**Author:** ![jaredgibb](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@jaredgibb](https://community.weweb.io/u/jaredgibb)\
**Post date:** [June 17, 2023, 3:51pm UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096/3 "2023-06-17T15:51:17Z")

</div>

ok. so an update would be that:

i opened the dev console → network tab

the response for my request is in fact only 50 objects

SO the weird thing is all the nulls in the array. they dont actually exist.

they seem more like placeholders.

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [June 17, 2023, 4:13pm UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096/4 "2023-06-17T16:13:42Z")

</div>

Yep, that’s what I suspected but it’s still a problem because it’s slowing you down in the editor so not a pleasant experience. The team will look into it for sure. We’ll keep you posted!

---

<div class="post-metadata">

**Author:** ![RCS](https://avatars.discourse-cdn.com/v4/letter/r/d2c977/32.png) [@RCS](https://community.weweb.io/u/RCS)\
**Post date:** [June 17, 2023, 8:23pm UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096/5 "2023-06-17T20:23:57Z")

</div>

Joyce, this seems to be widespread, it has messed up many of my formulas while trying to troubleshoot!

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [June 17, 2023, 9:34pm UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096/6 "2023-06-17T21:34:47Z")

</div>

Hi @RCS, this is not widespread. It is an issue specific to the Supabase data source plugin and does not affect formulas.

---

<div class="post-metadata">

**Author:** ![Alexis](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexis/32/13248_2.png) [@Alexis](https://community.weweb.io/u/Alexis)\
**Post date:** [June 23, 2023, 9:45am UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096/7 "2023-06-23T09:45:52Z")

</div>

Yeah they are placeholder because of how our collection engine works.

You have to bind the collection and not collection-\>data to access only the items from your current page

---

<div class="post-metadata">

**Author:** ![Wirajan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/wirajan/32/6438_2.png) [@Wirajan](https://community.weweb.io/u/Wirajan)\
**Post date:** [May 10, 2024, 10:45am UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096/8 "2024-05-10T10:45:39Z")

</div>

Hello. I have the same problem here [here](https://community.weweb.io/t/collection-from-supabase-pagination-bug/8539). I am using the collection, and not the collection → data… Is there any update on the bug?

---

<div class="post-metadata">

**Author:** ![Alexis](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexis/32/13248_2.png) [@Alexis](https://community.weweb.io/u/Alexis)\
**Post date:** [May 13, 2024, 9:17am UTC](https://community.weweb.io/t/weird-things-in-the-weweb-data-object-for-my-supabase-collection/3096/9 "2024-05-13T09:17:38Z")

</div>

Not a bug. When a collection is paginated we create an array containing as many items as you have on the unpaginated collection, then we fill it with null values and only the current page get fetched. It’s required for our internal logic to work. Then you have to bind the collection and not collection-\>data, you should receive an array containing only the data related to the current page
