Hello, I have completed further testing and found that the first proposed patch, 0001-fix-nested-virtual-database-result-identity.patch, is not required.
The issue can be fixed by the second patch alone: 0002-propagate-result-visibility-through-nested-virtual.patch. This patch introduces the dico_result_db_ex() callback, which accepts and propagates the result visibility flag through nested virtual databases. It also increments DICO_MODULE_VERSION to 4 while retaining the original dico_result_db() callback for backward compatibility. I have rebuilt the Docker image using Debian's Dico 2.12-3 source package with only this second patch applied. The resulting server was tested with the three-level ITBYLexicon virtual database: • GoldenDict: the test completed successfully. • A command-line DICT client: the test also completed successfully. • MIME headers are correctly returned when searching with the MIME option enabled. The Apache and Dico Docker images were rebuilt successfully, and the complete local Docker environment started without errors. Therefore, the first patch can be disregarded. The second patch alone provides the required fix. I am attaching the updated patch with the revised description. Best regards, Michael
0002-propagate-result-visibility-through-nested-virtual.patch
Description: 0002-propagate-result-visibility-through-nested-virtual.patch

