3 Nov
2014
3 Nov
'14
9:31 a.m.
Hi,
since the progressive search seems to start right away and for some reason our setup is too slow/too large to get instant SQL replies the answers seem to be dropping in as the SQL server finishes and them the client will render them as soon as it receives them.
This unfortunately gives answers for shorter strings later even if the search field already does seem to be filled with a longer query string.
Is there anyone who has implemented some JS/AJAX fix for this and ensure the answers processed by the client are only those matching the current search string (i.e. add a "static" version/revision/serial field into the SQL select and check for that in the results)?
Cheers, Kilian
--
Kilian Krause
Rechenzentrum Universität Stuttgart (RUS)
Abt. NKS - Netze und Kommunikationssysteme
Tel.: +49 (711) 685-64512
Fax.: +49 (711) 685-54512 (PC)
Fax.: +49 (711) 68 23 57
Allmandring 30a
70550 Stuttgart
DEUTSCHLAND