Paged Database Queries - Data Not Accessible on Client Side and Removal of Limits

I’ve recently had a couple of times I tried out using Paged Database Queries in a server action.

Each time, I found that:

1. Some database fields that were
   (a) listed in the query server action definition and
   (b) shown in the output data being shown in Chrome Developer tools as passing through to the client side
   Weren’t recognised by the Wappler client side, for example when referenced in a .where() function.

2. That if I changed the Database Query from being of type “Paged Records” to “Multiple Records” then paging information remained in the MySQL generated by the query (see screen shot below). There doesn’t appear any way to remove it again without re-building the query statement.

(I’m sorry that point (1) is a bit vague… I have a tight timescale I’m working to and decided not to spend any more time on trying to find out what was going on!)

If anyone can shine any light on what I experienced, or have had similar experiences I’d be really happy to hear about them… I don’t like to just give up on things!

Best wishes,
Antony.