v0.7.27 & v0.7.28 : FILTER broken -> Bug

[Chatweazle]

Antares 0.7.27 and 0.7.28 on Win10, accessing SQLite database:
Each time I click on the FILTER (magnifying glass) the first time after starting, Antares (as usual) prompts for input. No matter what I enter, the FILTER does not create a filtered output but *always' resets to the regular row/column view (as if I had "unclicked" the FILTER). Only when I repeat that step once more does Antares realize that I am trying to apply a filter and reacts accordingly, providing the resulting content rows.

0.7.27 and 0.7.28 are definitely broken; 0.7.25 (for example) works perfectly.

[Fabio286]

Hi @Chatweazle,
can you tell me if it appears something on debug console? To open the console click on "Console" on bottom right and go to "Debug console" tab.

[Chatweazle]

Hi there,

the DEBUG CONSOLE window remains empty. However, while I was at it, I checked the EXECUTED QUERIES window.
Here is a capture. The EXECUTED QUERIES window shows the following directly after Antares is loaded:

17:47:38: SELECT * FROM pragma_database_list
17:47:38: SELECT sqlite_version() AS version
17:47:38: SELECT * FROM "main"."honey" LIMIT 1000
17:47:38: SELECT * FROM "main".pragma_table_info('honey') WHERE pk != 0
17:47:38: SELECT * FROM "main".pragma_index_list('honey');
17:47:38: SELECT * FROM pragma_database_list
17:47:38: SELECT * FROM "main".sqlite_master WHERE type IN ('table', 'view') AND name NOT LIKE 'sqlite\_%' ESCAPE '\' ORDER BY name
17:47:38: SELECT * FROM "main".sqlite_master WHERE type='trigger'
17:47:38: SELECT COUNT(*) AS count FROM "main"."honey"
17:47:38: SELECT * FROM "main".pragma_table_info('honey')
17:47:38: SELECT * FROM "main".pragma_table_info('artists')
17:47:38: SELECT * FROM "main".pragma_table_info('honey') WHERE pk != 0
17:47:38: SELECT * FROM "main".pragma_index_list('honey');
17:47:38: SELECT * FROM "main".pragma_table_info('artists') WHERE pk != 0
17:47:38: SELECT * FROM "main".pragma_index_list('artists');
17:47:38: SELECT * FROM "main".pragma_foreign_key_list('honey');
17:47:38: SELECT * FROM "main".pragma_foreign_key_list('artists');

After I fired my FIRST request (which shows no output) this is added:

17:49:59: SELECT * FROM "main"."honey" WHERE "md1" LIKE '%ad-190%' LIMIT 1000
17:49:59: SELECT * FROM "main".pragma_table_info('honey') WHERE pk != 0
17:49:59: SELECT * FROM "main".pragma_index_list('honey');
17:49:59: SELECT * FROM "main"."honey" LIMIT 1000
17:49:59: SELECT * FROM "main".pragma_table_info('honey') WHERE pk != 0
17:49:59: SELECT * FROM "main".pragma_index_list('honey');
17:50:00: SELECT COUNT(*) AS count FROM "main"."honey"

Which seems weird, because when I fire my SECOND request (which successfully shows output) it only adds:

17:51:41: SELECT * FROM "main"."honey" WHERE "md1" LIKE '%ad-189%' LIMIT 1000
17:51:41: SELECT * FROM "main".pragma_table_info('honey') WHERE pk != 0
17:51:41: SELECT * FROM "main".pragma_index_list('honey');

This remains constant for every further request. Perhaps that helps you?
It does not matter if I search for "ad-189" or "ad-190" by the way, both are present in the db.

[Chatweazle]

(removed, comment Included in 1st post)

[Fabio286]

Which is your installation source? Exe installer or Microsoft store?

[Chatweazle]

Under Windows: exe installer from your website (standard install, NOT the portable).
I am momtarily using the Linux Flatpak version 0.7.25 without problems (installed via the Linux Mint 22 Software Manager)