Bug 371974 - Kexi erased some criteria of a query once a new field is added to the query
Summary: Kexi erased some criteria of a query once a new field is added to the query
Status: CLOSED DUPLICATE of bug 377579
Alias: None
Product: KEXI
Classification: Applications
Component: Queries (show other bugs)
Version: 2.9.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kexi Bugs
URL:
Keywords:
Depends on:
Blocks: 377579
  Show dependency treegraph
 
Reported: 2016-11-02 14:00 UTC by Begonia
Modified: 2017-04-10 11:06 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
step by step description of actions where search criteria was erased (2.23 KB, text/plain)
2016-11-02 14:00 UTC, Begonia
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Begonia 2016-11-02 14:00:08 UTC
Created attachment 101961 [details]
step by step description of actions where search criteria was erased

Application: kexi (2.9.7)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-45-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
<When a new field is added to a query, any criteria after the second AND is erased (even if the query was previously saved.>

Initial query criteria:
SELECT nometudiant, prenometudiant, fkmateria, FROM tbl_curso, tblcursoanomater, tblestudante WHERE tbl_curso.refgroupe = tblcursoanomater.fkcurso AND tbl_curso.refgroupe = tblestudante.fkgroupe AND (((tblcursoanomater.fkanocurso)=1))

One field, "libellegroupe", was added [using design screen], and then the last criteria is erased.

SELECT nometudiant, prenometudiant, fkmateria, libellegroupe, FROM tbl_curso, tblcursoanomater, tblestudante WHERE tbl_curso.refgroupe = tblcursoanomater.fkcurso AND tbl_curso.refgroupe = tblestudante.fkgroupe

see attachement for the rest of the description.
Comment 1 Jarosław Staniek 2016-11-02 14:12:09 UTC
Thanks.
Comment 2 Jarosław Staniek 2016-11-02 14:13:10 UTC
Templarary workaround: for certain more complex queries like this use only the SQL view.
Comment 3 Jarosław Staniek 2017-04-06 10:14:32 UTC

*** This bug has been marked as a duplicate of bug 377579 ***
Comment 4 Jarosław Staniek 2017-04-06 10:15:26 UTC
#377579 is newer but more general and fixed now for 3.0.2. So resolving this one too. Thanks.