Apache OpenOffice (AOO) Bugzilla – Issue 32715
"<>" filter doesn't work
Last modified: 2006-05-31 14:29:06 UTC
There is a form to access a MySQL database. If i create a filter rule [field] [<>] ['A'] i get an empty answer. If i recall the filter form, now the filter rule is [field] [=] ['<> A'] so there can't be a valid result.
correcting priority according to http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority - sorry, but this is *no* P1
Mathias, sorry, but I cannot reproduce it: - MySQL data source, therein a table with a text field, and a form for this table - open the form - enter the "form based filter" - enter "<> 'AAA'" in the control bound to the text field - apply the filter - re-enter the "form based filter" => "<> 'AAA'" is shown in the text field, as expected. Also, the filtered form showed the results as expected. Do you mind describing in more detail what you did, as well as more about your environment (table structure and the like). Please also consider reading http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html :)
Sorry for the incomplete description. I mean the filter in the database beamer. The field contains only a character (or not) (declared as string with length 1 in the table). For me (or better for the user, who can't create the wanted filter rules) it is P1. MySQL and SO7 runs on a (the same) W2k machine.
> For me (or better for the user, who can't create the wanted filter rules) it is > P1. I understand this, but with this attitude nearly everything is a P1, since every bug is serious to somebody. You'd certainly agree that this would render the priority system useless. In the data source browser, I could indeed reproduce this. I'm going to attach a bug doc.
Created attachment 17014 [details] MySQL script to generate a sample table
confirming, assigning, targeting. Steps to reproduce: - with a MySQL database of your choice, import the attached i32715.sql to create a sample table. Alternatively, simply create a table with some text field manually. - create a MySQL/ODBC data source for this database - display the table "i32715" in the data source browser - press the "Default filter ..." button => the filter dialog pops up - ensure that in the first line of the dialog, "Field" is set to "txt", "Condition" to "<>", and "Value" to "'A'" - close the dialog with OK => the table is properly filtered - re-open the dialog => in the first line, "Condition" is now "=", and "Value" is "<> 'A'", which obviously is not what you intended ... Tried this in 1.1.2, as well as in 680m49 non-product - reproducible in both versions. In a non-product version, there's also an assertion saying "Wrong node type" from dbaccess/source/core/api/SingleSelectQueryComposer.cxx, line 822. fs->oj: seems that OSingleSelectQueryComposer::getPredicateType should also care for SQL_NODE_NOTEQUAL ....
.
Reopen for QA
Please verify. Thanks.
Set to fix again
Thanks. (Sorry, cannot verify at the moment.)
Hi, verified in cws dba16. Bye Marc
Hi, fixed in current developer build -> close. The current developer build can be found at http://download.openoffice.org/680/index.html Feel free to reopen if this issue is not fixed in the developer build. Bye Marc