To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=85311
User mhatheoo changed the following:
What |Old value |New value
================================================================================
Status|RESOLVED |UNCONFIRMED
--------------------------------------------------------------------------------
Resolution|WORKSFORME |
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed May 21 16:53:59 +0000
2008 -------
=> atj
well, this is no solution for the problem, and I am not sure whther you really
got the problem:
The case is about tables, that already exist, and for these, not the HSQLB
itself but the front-end/integration from OO is behaving wrong.
The solution is as stated before and can be done within a SQL-statement only.
Wihin ANSI-SQL indexed fields should always be treated case-unsensetive, while
sorting or using as temporary-index on un-indexed fields should be
case-sensetive. That are rules. But as OO-Base is not using indexes on
DBase-files, every field in a query is - sofar - treated case-sensetive.
my proposal was, that OO should work the other way round and treat fields
case-unsensetiv by default.
However - no solution for DBASE-files - I reopend the issue.
Martin
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
