0

Hello World,

I'm in research mode for one of feature to be built in our software and there one new thing that we have never faced.

The thing is, on one form we have a drop down with list of items. User can select default which means all items needs to be considered or else he can selectively opt for certain list items.

Actually the form is related to filter functionality depending upon users input the data is going to get filtered and displayed on UI.

The main problem we are trying to solve is suppose user selects default, which means all list items ID's are gonna be considered in POST call of API. The list can be huge, say 1 to 1K and above too.

So under such circumstances we can build the query string but, it seems its gonna be so huge. I have also studied that certain browsers support limited query string as per their standard limits.

So currently I have following doubts in mind.

  1. Will shortening of query string work here ?
  2. By which technique it can be handled efficiently ?
  3. What performance considerations I need to take care during during so ?

Any suggestions or thoughts are welcome. That would boast my software design thinking.

Aԃιƚყα Gυɾαʋ
  • 107
  • 1
  • 15
  • query string usually implies a database query... it's not real clear if you are asking about query values in a GET, or a standard database query. You mention POST... so you can simply post something like "ALL" and parse the logic from there. A query string could also use the same logic that the interface uses to get the IDs. You may want to include some code. I think it would help clarify the question a bit. – pcalkins May 23 '22 at 18:25

1 Answers1

1

based on what I understand from your question, here is my opinion:[if I understood wrong, please correct me, so I can help you]
You need to send query in URL and not in body or using JSON!is that correct?
I think you don't need to send every one of the selected items one by one! If there are selected in serial, you can perform a range in your query!
Like http://abcd/test?id=1-43,6-765(take ID as string and then export the useful data in back-end) with this approach, you can shorten your query!
And also think about the database too (if there is any).querying this much data is use a lot of IO and make query low performance.

Hussein Beygi
  • 391
  • 2
  • 7
  • You correctly got my intention sir. The idea of shortening by range is cool. But it can have many scenarios involved one is like that drop down has 5 objects but when their ids are sorted those can be 1,3,6,8,9 so now the main concern at backend will be 1-9 does not mean 1,2,3,4,6,7,8,9. Thats where things may get wrong. but idea is cool if this scenario would have not existed at my backend. – Aԃιƚყα Gυɾαʋ May 25 '22 at 14:22
  • Take look at this article, I think that might help you for decide https://stackoverflow.com/questions/812925/what-is-the-maximum-possible-length-of-a-query-string?rq=1 – Hussein Beygi May 25 '22 at 17:07