The foundset updater is very fast to update a field after I made a search in a normal table field. (runs in 1 second, 30000 records)
But if I use a related field for search then the foundset updater really runs slowly so that it freezes the solution for a while. (runs in around a bit less than a minute, 1300 records).
Thanks!
I think the foundsetUpdater just fires a (update) query. Depending on the (select) query that leads to the foundset, this can take shorter or longer. I don’t think there is much Servoy can optimize…
I thought the same way too. But it was a bit of strange for me since the relational query updates should not take that long. I can the see the searches are damn fast and do not understand why the updates are slow.
Check the performance data in the server-admin to see what query is fired when you run the updater. Then it should be clear why it takes so long.
Just tested the performance data:
1> related field search:
update finance set is_myob_updated=? where finance_id = ? (00:00:046, count: 75) The actual no of records in the foundset is also 75 (correct). The actual time taken was about 1 minute (strange).
2> normal field search
update finance set is_myob_updated=? where status = ? (00:00:406, count: 1) The count says 1 but the actual no of records in my foundset was 887
Very strange.
In the update 1 the search previous to the update was done on a related field . But the where condition there is using the primary key.