<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:robert@familiegrosskopf.de" title="Robert Großkopf <robert@familiegrosskopf.de>"> <span class="fn">Robert Großkopf</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - EDITING In the base query designer I would like to be able to request it to parse down the criterion of a column"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134049">bug 134049</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Version</td>
<td>6.0.7.3 release
</td>
<td>Inherited From OOo
</td>
</tr>
<tr>
<td style="text-align:right;">Ever confirmed</td>
<td>
</td>
<td>1
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>UNCONFIRMED
</td>
<td>NEW
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>robert@familiegrosskopf.de
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - EDITING In the base query designer I would like to be able to request it to parse down the criterion of a column"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134049#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - EDITING In the base query designer I would like to be able to request it to parse down the criterion of a column"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134049">bug 134049</a>
from <span class="vcard"><a class="email" href="mailto:robert@familiegrosskopf.de" title="Robert Großkopf <robert@familiegrosskopf.de>"> <span class="fn">Robert Großkopf</span></a>
</span></b>
<pre>This is a feature request.
The GUI couldn't create such a code. It creates a code like
SELECT * FROM "Table1"
WHERE "FieldA" = :AskA AND "FieldB" = :AskB
OR "FieldA" = :AskA AND "FieldB" = IS NULL
OR "FieldA" IS NULL AND "FieldB" = :AskB
OR "FieldA" IS NULL AND "FieldB" = IS NULL
With this code nearly the whole possible rows for criteria in the designer will
be blocked. Adding a third field will be impossible in the designer.
SELECT * FROM "Table1"
WHERE ( "FieldA" = :AskA OR "FieldA" IS NULL) AND
("FieldB" = :AskB OR "FieldB" IS NULL )
This all works well without the GUI. The query doesn't need to be switched to
direct SQL. You could input data ...
I could confirm the behavior of the GUI. Would be a good idea to let the user
decide if he wants to set the columns of the query-GUI in brackets. At this
moment the GUI looks first for the rows, adds all content with "AND" and then
adds the next row with "OR".
This behavior exists since the beginning of LO, so I set the version to
"Inherited from OOo"</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>