Posts

Nigel:

Administration/Batch update/Search and replace begins a search as soon as an entry is made in the search field and before the replace field is entered. When doing a large number of these on a 17,000 plus individuals data base, search takes some time. It is really a pain to have to wait for 2 searches for each change. Any way I can stop this from happening?

Thanks

Roy

Apache 2.4.27  PHP 7.19 MariaDB 10.2.8

The short answer is no, it’s the way this tool was designed. So whilst it “might” be possible to change it, that’s not something high on my priorities so far. It was specifically done this way to make the function actually practical on large trees, on servers with more limited resources.

But I’m puzzled by (or misunderstanding) the statement “It is really a pain to have to wait for 2 searches for each change.”

You only need to do this for the first record. Then with “Update”, or “update all” you can apply the same search and replace to all other matching records. If it’s not working like that w should investigate.

Nigel
My personal kiwitrees site is www.our-families.info

kiwi wrote:

So whilst it “might” be possible to change it, that’s not something high on my priorities so far.

Actually, I might take that back. Just had a fresh look at the code, and there might be a way to improve this (you are certainly not the first to ask). Can you send me a couple of examples of the task you are trying to achieve so I can test the idea on your issue specifically?

Nigel
My personal kiwitrees site is www.our-families.info

Nigel:

Wasn’t trying to do anything special; just a simple search and replace. By trial and error have come up with procedure work arounds.

The natural thing to do is enter the “search” phrase which triggers the program to search. After waiting for that and entering the “replace” phrase, you wait again for it to search. The work around is to do it backwards and enter the “replace” phrase first; the program then does a quick fresh. Then enter the “search” phrase.

Because of the current behavior, the following work around for repetitive search and replace actions is also necessary. Clear the previous “search” phrase which triggers a quick refresh. Replace the earlier “replace” phrase with the new one; another quick refresh. Lastly, enter the new “search” phrase.

If there is not much use of this program feature, a change certainly is not necessary. However, to avoid one of the two search times the user cannot use the intuitive approach

Roy

Apache 2.4.27  PHP 7.19 MariaDB 10.2.8

Roy wrote:

If there is not much use of this program feature, a change certainly is not necessary.

On the contrary. I believe it us a very commonly used tool. Hopefully my new idea (mentioned above) will help.

Nigel
My personal kiwitrees site is www.our-families.info

Nigel:

Thanks for the Search and Replace change in 3.3.2. It works well, saving time on a large database. I don’t know why but it seems to complete the search faster too.

Thanks again

Roy

Apache 2.4.27  PHP 7.19 MariaDB 10.2.8