Add query results in an page Array component... Acceptable method?

[famousmag]

Hey guys,

I'm working on something and my knowledge is not enough to undestand if what I'm trying to do is "wrong" or "not a good method"...

So, as my title says, if we add the results of a query to an Array component in our page, would that be appropriate or not?

How can we check the impact of that method on the user end?
I don't have a large dataset to check it and also I can't check on mobile devices what happens...
And the most important I don't know how to check it...

Off course you would ask "how large is the data you want to add?
That's what I'm trying to figure out and then maybe I can set a limit on that functionality...

Anybody can give me an idea of what can happen in that case?

Thanks in advance

[famousmag]

What I'm working on is a kind of infinite scrolling
(no matter if the loading occures on scrolling or on button clicking)

So, something like our community forum "load more" topics handles the loading of the topics...
Here is a short video of my attempt (but with only 26 records...)

Every time the query reurns 10 records but they get added to the existing records list of the table in my page

[Hyperbytes]

I dont think this method will be much dufferent to a query JSON response in relation to dataset size so i guess my answer would be, if you would deal with a query that size then in array form would be acceptable.

[famousmag]

Thanks Brian for your feedback!

From what I undesrstand from your answer, since the serverconnect everytime is loading only xx results, all I have to pay attention is the Array to not be overload...
Just like loading straight forward a query with 2000 records (without pagination it is not suggested)...

Beside I was wondering, where are the query results loaded so they are available in our page?
Instead of holding all the amount of data there, hold them in our Array...

Am I correct brother?

[Apple]

@famousmag

So, as my title says, if we add the results of a query to an Array component in our page, would that be appropriate or not?

There's nothing inherently wrong, but often choices like this will let you discover things ("Wappler bugs") such as missing schema

@famousmag

Beside I was wondering, where are the query results loaded so they are available in our page?

In your server connect data variable? I don't understand the question

[famousmag]

hey @Apple,

There was a schema issue but I populated the serverconnect on my table generator...
Since the "schema" I'm using is the one from the serverconnect...

If you have time please see a few explenations here:

"Load more" functionality... Like Wappler chat

I have a table Notifications with some columns and a subtable that is updated if a Notification is SENT to the user(not_usr_sent==1) and if is READ by the user(not_usr_read==1). [Screenshot_1] So, first I created the serveraction that reads the notifications. [Screenshot_2] We need 2 $_GET variables: page: holds the current page of results limit: defines the amount of records returned on each call We define 2 setValue for those two variables and set their default values We have a query …

[Hyperbytes]

@famousmag

Beside I was wondering, where are the query results loaded so they are available in our page?
Instead of holding all the amount of data there, hold them in our Array...

Not quite sure what you mean but

as you load records in sets of 10, each old query data will be overwritten so you will never store more than 10 as JSON.

Your array will of course grow as you page through.

Alternatively you could just repeat the same paged query over and over again but changing the limit parameter to 10 bigger each cycle.

This will have a bigger data overhead but would be easier to implement i think. Database server speed would be a huge factor if re-running the paged query each time.

[Apple]

@famousmag

If you have time

Next time. Good luck with your current issue!