Issue 114566 - query wizard: cannot set (anymore) conditions other than "equal"
Summary: query wizard: cannot set (anymore) conditions other than "equal"
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 3.3 Beta 1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.3
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks: 111112
  Show dependency tree
 
Reported: 2010-09-17 09:55 UTC by Frank Schönheit
Modified: 2010-10-15 11:01 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
document to reproduce the bug case (2.73 KB, application/vnd.sun.xml.base)
2010-09-17 09:55 UTC, Frank Schönheit 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2010-09-17 09:55:21 UTC 
- open the attached database document
- select "Queries" on the left hand side
- select "Use Wizard to Create Query" in the task pane
- in the query wizard
  - on the first page, move all fields to the right
  - advance to the "Search Conditions" page
  - in the first condition, select "names.ID" as field, and "is not equal to"
    as condition. Enter an arbitrary numeric value in the "Value" field
  - advance to the "Overview" page
=> note that it says "Search conditions: ID is not equal to <> 3" - this is
   already strange
  - finish the wizard
=> you get an error message saying something about a syntax error in
     SELECT "names"."ID" AS "ID", "names"."name" AS "name"
     FROM "names" "names" WHERE ("names"."ID" <> <> 3)
   (Well, that error message is right)
=> the query is not created

This happens with all conditions except equal, not/like, not/null
Comment 1 Frank Schönheit 2010-09-17 09:55:51 UTC 
Created attachment 71747 [details]
document to reproduce the bug case
Comment 2 Frank Schönheit 2010-09-17 09:57:21 UTC 
worked fine in 3.2.1 => keyword regression
Comment 3 Frank Schönheit 2010-09-17 10:03:56 UTC 
fs->oj: The problem here seems to be that the query composer returns an invalid
structured filter: The single condition delivered by the component is
  Name: "ID"
  Handle: 2 (SQLFilterOperator.NOT_EQUAL)
  Value: "<> 3"
=> the "Value" is wrong, it should be "3" only, not "<> 3"
Comment 4 ocke.janssen 2010-09-20 07:14:48 UTC 
Set as duplicate.

*** This issue has been marked as a duplicate of 114273 ***
Comment 5 ocke.janssen 2010-09-20 07:16:59 UTC 
Closing.
Comment 6 Frank Schönheit 2010-09-20 08:13:13 UTC 
no, those are different issues, sorry :)
Comment 7 Frank Schönheit 2010-09-20 08:13:56 UTC 
back to NEW
Comment 8 Frank Schönheit 2010-09-20 11:34:11 UTC 
have a patch, which fixes all condition types except "is not null", which has
yet another root cause. Submitted this as issue 114617.
Comment 9 Frank Schönheit 2010-09-20 11:34:42 UTC 
grabbing
Comment 10 mdxonefour 2010-09-20 11:48:43 UTC 
adjusting target
Comment 11 Frank Schönheit 2010-09-20 11:54:23 UTC 
fixed in CWS dba33j

find more information about this CWS, like when it is available in the master
builds, in EIS, the Environment Information System:
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300/dba33j
Comment 12 Frank Schönheit 2010-09-20 11:56:28 UTC 
oops, didn't want to revert the target - had the old value still in the browser ...
Comment 13 Frank Schönheit 2010-09-23 08:31:07 UTC 
fs->msc: please verify in CWS dba33j
Comment 14 marc.neumann 2010-09-27 10:10:09 UTC 
verified in CWS dba33j

find more information about this CWS, like when it is available in the master
builds, in EIS, the Environment Information System:
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300/dba33j
Comment 15 r4zoli 2010-10-15 11:01:49 UTC 
Checked in OOO330m10, Ok. Closing.