View Full Version : Why do unbuffered stores send page, limit and start options to the backend?

24 May 2014, 9:26 PM
If start and limit are passed to the server, it will usually apply OFFSET and LIMIT in the database queries, even though the store is not capable of automatically asking for more data, so only the first page is ever displayed.

Why was Ext.data.Store designed this way? What am I missing?

27 May 2014, 9:52 AM
If you want to stop the start, limit and page params from being sent, you can set these configs to false on the proxy: startParam, limitParam, pageParam

28 May 2014, 12:22 PM
While this doesn't answer my original question, it does provide a workaround. Thank you.

I wonder if backend code is always supposed to know whether to respect the start/limit or not, or if front end developers are always supposed to explicitly disable these parameters? Either way, looks like bad design to me.

28 May 2014, 12:23 PM
I would say backend code should only return what is requested so it's up to the client side to handle this.