The idea behind it was that SQLSearchView solves the case where you don't want to build the index on the device as it is too slow (relevant for large indices). So you build the db index with B4J and use it on the mobile devices.
Hello Erel, I see where you are coming from with the above statement. In my case the data is from an online API that returns a long list that then needs extra filtering before sending another API request.
The thing is that the B4XSerializator link below advises to use SQLSearchView, so that's what I did
Better to use: https://www.b4x.com/android/forum/threads/b4x-sqlsearchview-sqlite-based-search-view.133379/ Two very important methods were added to B4XSerializator in RandomAccessFile v2.20: ConvertObjectToBytesAsync and ConvertBytesToObjectAsync. With these methods you can asynchronously...
Okay I'll keep looking and trying solutions, but the chances are that I'll just create a solution as I don't like modifying B4X libraries as once that library has been updated I'll have to modify it again.
Thank you and have a nice day Erel