Posted by Bocah Sableng on 04/27/07 12:48

On Apr 27, 8:39 am, "Vince Morgan" <vin...@REMOVEoptusnet.com.au>
wrote:
> Please forgive the off topic content.
> I'm working on redesigning an ecommerce site written by someone else in the
> near future.
> Currently a user can choose a product group and select items from a returned
> list. I noticed that on many of these groups the number of items to choose
> from topped out at 200, when in fact the actual number of those items could
> be as many as 5000.
> Perfectly adequate if you only ever needed items in the lower range of those
> beginning with "a".
> When I asked the owner of the site why this was so, he said the original
> develloper did this to speed things up because it was too slow.
> Fortunately, a customer can access the products they may actualy want via
> other means.
> Finding this was easy, but fixing it has left me scratching my head
> Acutaly, I _hope_ that's why I'm scratching my head ; @@
> Currently the query selects the top 200 records sorted on the item names.
> Before I dive headlong into this I would be very gratefull to see the
> thoughts of others who know of workable solutions.
> TIA
> Vince

Why don't you provide a inputbox for searchable select list?
When the user choose a product group, enter a string in the input, and
click a submit button, the page refresh and your select item only
contain the product name match with user's product group and input
string. For optimization, the initial select item is empty and only
filled if user's string length minimal 3 characters. You can put the
inputbox and the select list in different forms. If its performance
still poor, consider using AJAX.
Sorry for the messy english.
HTH

[Back to original message]