Issue 57435 - Unable to query on boolian fields
Summary: Unable to query on boolian fields
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0
Hardware: All All
: P3 Trivial with 6 votes (vote)
Target Milestone: OOo 2.1
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords:
: 63076 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-11-06 17:08 UTC by geoff_stansfield
Modified: 2007-02-02 13:00 UTC (History)
2 users (show)

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

Attachments
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 geoff_stansfield 2005-11-06 17:08:56 UTC 
I have downloaded OOo_2.0.0_Win32Intel_install.exe & installed on a Win
2000 Pro machine. I have checked the MD5sum and that is fine. 

Use "Wizard to create Query", select the required table and those fields
with File Type set to Yes/No [BOOLEAN] are not on the list of Available
Fields.

Use "Create Query in Design View", select the required table and the
fields with File Type set to Yes/No [BOOLEAN] are available for
selection - but finding a criterion that works is not easy.

These examples work :
SELECT "id", "fred", "george", "flag" FROM "Table1" "Table1" WHERE (( "flag" =
False ))
SELECT "id", "fred", "george", "flag" FROM "Table1" "Table1" WHERE (( "flag" =
True ))

but I can only enter/modify the WHERE clause in SQL view mode. That done, I 
can toggle design view on/off - and see FALSE (or TRUE) in the criterion 
field, but if I edit the criterion I get "Warning. Syntax error in SQL
statement" and the query will not parse/run/save.
Comment 1 marc.neumann 2005-11-08 09:59:47 UTC 
Hi,

the first part that bool fields are not displayed in the wizard is issue 47418.

The second part I can reproduce. 

I reassign the issue to the right developer.

Bye Marc
Comment 2 ocke.janssen 2005-12-30 08:17:22 UTC 
Fixed in cws dba30.
Comment 3 alex.thurgood 2006-01-06 11:00:53 UTC 
Hi,

There appear to be quite a few people waiting for this particular problem to be
fixed, see for example :

http://www.oooforum.org/forum/viewtopic.phtml?t=29731&sid=ae59398a44b95a085eeedb9155b45cf3

And also on the French users n-l list. Any idea when this is likely to
integrated into head and qa'ed ? OOo Later isn't much help at the moment ?

TIA,

Alex
Comment 4 ocke.janssen 2006-01-06 11:04:18 UTC 
Hi Alex,

If we get enough votes for this issue, it is no problem to get this fix into the
PP2. 

Best regards,

Ocke
Comment 5 Regina Henschel 2006-03-12 13:41:19 UTC 
*** Issue 63076 has been marked as a duplicate of this issue. ***
Comment 6 Frank Schönheit 2006-05-11 13:55:36 UTC 
fs-> msc: please verify in CWS dba30

re-open issue and reassign to msc
Comment 7 Frank Schönheit 2006-05-11 13:55:40 UTC 
reassign to msc
Comment 8 Frank Schönheit 2006-05-11 13:55:44 UTC 
reset resolution to FIXED
Comment 9 Frank Schönheit 2006-05-12 07:35:39 UTC 
targeting to 2.0.4, as the fix is already available, and has meanwhile been
checked in in a 2.0.4-CWS
Comment 10 Frank Schönheit 2006-05-12 07:37:51 UTC 
targeting to 2.0.4, as the fix is already available, and has meanwhile been
checked in in a 2.0.4-CWS
Comment 11 marc.neumann 2006-05-18 08:55:20 UTC 
verified in cws dba30

You can found more information about this CWS in the EIS tool at
http://eis.services.openoffice.org/EIS2/cws.SearchCWS
Comment 12 Frank Schönheit 2006-08-11 11:22:30 UTC 
targeting to 2.1, since the fix is part of a CWS aiming for this release
Comment 13 marc.neumann 2007-02-02 13:00:58 UTC 
Hi,

this is fixed in the current master. The current master is available at
http://download.openoffice.org/680/index.html

I close this issue now.

Bye Marc