Issue 92117 - (german:)Autofilter kann nicht mehr nach Boolean filtern
Summary: (german:)Autofilter kann nicht mehr nach Boolean filtern
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.4.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: regression
: 93165 (view as issue list)
Depends on:
Blocks:
 
Reported: 2008-07-25 08:56 UTC by mlebek
Modified: 2010-02-22 14:43 UTC (History)
1 user (show)

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


Attachments
document to reproduce the bug case (4.17 KB, application/vnd.sun.xml.base)
2008-07-28 08:52 UTC, Frank Schönheit
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description mlebek 2008-07-25 08:56:14 UTC
Wenn man in einer Abfrage versucht, mit dem Autofilter nach einem Boolean Wert
zu filtern, erhält man folgende Fehlermeldung:

Fehler beim Setzen der Filter-Kriterien
SQL-Status: HY000
Fehler-Code: 1000

Syntax error in SQL expression
SELECT "ID", "Name", "ausgeschieden" FROM "Tabelle1" WHERE
"Tabelle1"."ausgeschieden" = 1 = 1
syntax error, unexpected SQL_EQUAL, expecting $end

Der Fehler besteht seit 2.4.1.
Comment 1 Frank Schönheit 2008-07-28 08:52:44 UTC
Created attachment 55398 [details]
document to reproduce the bug case
Comment 2 Frank Schönheit 2008-07-28 08:55:07 UTC
(please note that the language of choice in IssueZilla is English. You will not
always have the luck some German native speaker will first encounter your issue ...)

English issue description:
- open the attached database document
- open the contained table by double-clicking it
- in the table data view, move the cursor to the boolean column
- press the "Auto Filter..." button in the toolbar
=> a message box pops up saying something about a syntax error
Comment 3 Frank Schönheit 2008-07-28 08:57:06 UTC
adding "regression" keyword - the scenario used to work in OOo 2.3.1, but not in
OOo 2.4/.1.
Targeting, correcting priority
(http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority)
Comment 4 Frank Schönheit 2008-08-21 09:33:27 UTC
fs->oj: please take this ...
Comment 5 ocke.janssen 2008-08-21 11:53:30 UTC
Fixed in cws dba31c
Comment 6 ocke.janssen 2008-08-27 12:13:36 UTC
*** Issue 93165 has been marked as a duplicate of this issue. ***
Comment 7 ocke.janssen 2008-11-04 11:10:31 UTC
Please verify. Thanks.
Comment 8 marc.neumann 2008-11-14 14:17:49 UTC
verified in CWS dba31e

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%2Fdba31e
Comment 9 thorsten.ziehm 2009-07-20 14:52:26 UTC
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
http://download.openoffice.org/index.html
If you want to know more about the handling of fixed/verified issues =>
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues
Comment 10 thorsten.ziehm 2009-07-20 15:36:26 UTC
Sorry this issue was wrongly closed. This issue will be reopened automatically.
And will be set after that back to fixed/verified.
Comment 11 thorsten.ziehm 2009-07-20 15:40:44 UTC
Set to state 'fixed'.
Comment 12 thorsten.ziehm 2009-07-20 15:44:43 UTC
Set back to state 'verified/fixed'.

Again. Sorry for the mass of mails.
Comment 13 thorsten.ziehm 2010-02-22 14:43:49 UTC
This issue is closed automatically. It should be fixed in a version with is
available for longer than half a year (OOo 3.1). If you think this issue isn't
fixed in the current version (OOo 3.2) please reopen it. But then please pay
attention about the field 'target milestone'.
The closure was approved by the Release Status Meeting at 22nd of February 2010
and it is based on the issue handling guideline for fixed/verified issues  : 
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues