pawelsalawa / sqlitestudio

A free, open source, multi-platform SQLite database manager.
https://sqlitestudio.pl
Other
4.67k stars 571 forks source link

Filter can't show result #5099

Closed gmuskie closed 4 days ago

gmuskie commented 1 week ago

Details

After entering the filter text in Views, can't see any result. Not sure it is related to https://github.com/pawelsalawa/sqlitestudio/issues/4641 or not.

Before filter: image

After filtered: image

Steps to reproduce

I've a view and entered the filter text in Data grid and no result after applied

Operating system

Windows 10

SQLiteStudio version

3.4.4

tuffnatty commented 1 week ago

Case sensitivity problem?

gmuskie commented 1 week ago

It's not case sensitivity issue. No matter upper case or lower case, nothing show up:

image

pawelsalawa commented 1 week ago

Can you please show DDL of this view?

gmuskie commented 1 week ago

Here you go: CREATE VIEW v_switch_port_to_data_port AS SELECT i.description AS switch_description, i.hostname AS hostname_or_usage, s.switch_port_number AS port_no, x.name AS to_panel_port, x.jack_position AS cubicle_jack_position, x.firstname, x.lastname, y.category || " | " || y.description || " | " || COALESCE(y.hostname, '') || " | " || COALESCE(y.remark, '') AS to_device FROM switch_port s LEFT JOIN inventory i ON i.inventory_id = s.inventory_id LEFT JOIN inventory y ON y.inventory_id = s.device_id LEFT JOIN ( SELECT d.data_port_id, d.name, d.jack_position, j.location_name, j.firstname, j.lastname FROM network_port AS d LEFT JOIN ( SELECT l.location_id, l.name AS location_name, e.firstname, e.lastname FROM location l LEFT JOIN employee e ON e.employee_id = l.employee_id ) j ON j.location_id = d.location_id ) x ON x.data_port_id = s.data_port_id;

pawelsalawa commented 1 week ago

Okay, I think I found the problem. It looks like the filter works for the 1st time when you just open the View window, but then any subsequent attempts to filter will return empty results.

It obviously is a bug and will be fixed.

pawelsalawa commented 4 days ago

It looks like this is fixed by the way of fixing #5065. At least I can no longer reproduce it now as I have the #5065 fixed.

gmuskie commented 4 days ago

Thanks. Will check it when 3.4.5 is ready.