| Summary: | Complex WHERE conditions such as (x=a AND y=b) not supported in Query Designer | ||
|---|---|---|---|
| Product: | [Applications] KEXI | Reporter: | robert leleu <robert.jean.leleu> |
| Component: | Queries | Assignee: | Jarosław Staniek <staniek> |
| Status: | ASSIGNED --- | ||
| Severity: | normal | CC: | adam, inksi, joseph, staniek |
| Priority: | NOR | Keywords: | efficiency-and-performance |
| Version First Reported In: | 2.5.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | data base required to check my comment | ||
|
Description
robert leleu
2013-02-09 15:21:38 UTC
Dear Robert, thanks for reporting. Should you be able to create a small database exposing the problem, please attach it to this bug to help me fix the bug faster. I did create from scratch a small base, and could not reproduce. Should I try to prepare the small base from my actual base by 1/ suppressing tables not involved 2/ having only a few lines in each table ? thanks Robert, yes please if you can, thanks. Created attachment 77137 [details]
data base required to check my comment
the attached file is a kexi database, a type not in the list
and here is the associated comment take a copy of the attached file «adressesreduit.kexi» before trial edit query liensidentite you see :(links between same name fields ; criteria 1029 into field liens.licleunik) switch to data liensidentite it's OK (12 rows) edit SQL to AND (liens.licleunik = 1029 or liens.licleunik = 1028) save switch to data, it's OK (17 rows) switch to edit there is no links between the tables open SQL edit «AND (liens.licleunik = 1029 or liens.licleunik = 1028)» is no longer present switch to data hangs close query (while hanging), crashes Thanks for the quality feedback Robert, this really helps. I'll get back to you ASAP. Updated title to a real reason: Complex WHERE conditions such as (x=a AND y=b) not supported in Query Designer Fixing this is not too easy for the minor version 2.9.x. Rather in 3.x. Current workaround is to use the SQL view for this kind of queries. However, for 2.9.11 there's no crash, so changing severity to Normal. Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. @Justin This bug was confirmed and even assigned. I'd like to be sure we do not click Resolved and loosing all the investigations documented here. |