To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114187
------- Additional comments from amel...@openoffice.org Thu Sep 2 17:35:21 +0000 2010 ------- "in the long *term*" that should read. Not sure how Freud would interpret that slip! As for the long term, my first instinct is that it shouldn't be too complicated to implement it. Instead of sending a revised version of the original query (which OO wouldn't be able to do, since it isn't parsing the original query), OO could create a new query that selected from the original as a subquery -- SELECT * FROM (original query) WHERE (new filter conditions) ORDER BY (new sort order). You wouldn't be able to remove existing filter conditions, only filter amongst the results you have, but I think that is a reasonably intuitive behaviour. There's just one difficulty -- issue 114188 , at least when dealing with the embedded DB. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
