Bug: SearchExecutor in Entity suggestion field is delayed by one keypress

jamie.guthrie · January 16, 2025, 9:49am

I have a strange bug, which only applies on our production system, and not locally or on our test environment.

When entering characters into the EntitySuggestionField, the suggested values are one keypress behind. i.e. searching typing in 1 → 12 → 123 will do a search for “12”

I’ve attached a video of this in action. Strangely it only happens on production, which leads me to believe that it might be something to do with how quickly requests are made to the database, and whether the data is received back in time, but it seems strange regardless

jmix_searchexecutor

Any ideas what might be causing it, or how to fix it?

shchienko · January 20, 2025, 12:54pm

Hello,

I am attaching a ticket so you can track progress.

github.com/jmix-framework/jmix

Search Executor is delayed by one keypress

opened 10:49AM - 16 Jan 25 UTC

jguthrie100

type: bug in: ui triage

### Environment Jmix version: 1.3.5 ### Bug Description When entering charact…ers in an Entity Suggestion Field with a searchExecutor, the search is delayed by one keypress. i.e. typing 1 -> 12 -> 123 will only do a search for "12". Strangely this only occurs on our production server, and not our test server, or when running locally. ![Image](https://github.com/user-attachments/assets/90ec5b19-2475-4518-9d9c-f4c4c0c81d98) The bug occurs in 2 places, and runs off the following code: ` public List<Material> loadMaterialsContainsMaterialNumber(String materialNumber, Integer limit) { if (limit == null || limit < 0) { limit = Integer.MAX_VALUE; } return dataManager .load(Material.class) .condition(PropertyCondition.contains(Material.Fields.material_number, materialNumber)) .maxResults(limit) .list(); } ` ` public List<CustomMaterial> loadCustomMaterialsStartsWithId(String customMaterialId, Integer limit) { if (limit == null || limit < 0) { limit = Integer.MAX_VALUE; } // Have to run a raw sql query first, as Jmix jpql doesn't allow casting id to text (so can't do a LIKE search) List<Long> customMaterialIds = jdbcTemplate .queryForList("select id from cmat.cmat_custom_material where id::text LIKE ? ORDER BY id ASC LIMIT ?", Long.class, customMaterialId.concat("%"), limit); if (customMaterialIds.isEmpty()) { return Collections.emptyList(); } return dataManager .load(CustomMaterial.class) .condition(PropertyCondition.inList(CustomMaterial.Fields.id, customMaterialIds)) .sort(Sort.by("id")) .maxResults(limit) .list(); } `

Regards,
Nikita