Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | App - FluidShell |
| Version | Future - PM |
Table & column names seem to be case-insensitive in SQLite, however if having created, for instance, a table with lowercase chars and then using a select with uppercase chars, the pop-up window does not stay up.
Example: (^ = pressing the Tab key)
$ create table test_lc (col_lc text) /
$ select * from T^<---The pop-up window correctly appears
$ select * from T^e<---However, if after the Tab key, the next char is typed, the pop-up disappears, it should stay up
$ select * from test_lc where C^
$ select * from test_lc where C^o<---Similar for columns
I am not familiar with auto-completion related code. I traced the code and it seems to me FS auto-completion popup does not have any DB server related information; hence, to handle your test case, I made change so that the match-comparison performed in the popup is case-insensitive (it seems to me this is the way how match-comparison is implemented in the Query Analyzer's auto-completion popup). SVN r30651.
I need to re-open this issue, I forgot to test r30651 against UNIX auto-completion. FS auto-completion popup is shared by FS UNIX auto-completion (match commands, variables, files, etc) and FS SQL auto-completion where UNIX auto-completion probably should be case-sensitive while SQL auto-completion likely should be case-insensitive. r30651 always performs a case-insensitive match that probably is not we want.
I need to re-open this issue, I forgot to test r30651 against UNIX auto-completion. FS auto-completion popup is shared by FS UNIX auto-completion (match commands, variables, files, etc) and FS SQL auto-completion where UNIX auto-completion probably should be case-sensitive while SQL auto-completion likely should be case-insensitive. r30651 always performs a case-insensitive match that probably is not we want.
Made change, SVN r30666, so that case-insensitive match is performed for SQL commands and case-sesitive match is performed for everything else.
Made change, SVN r30666, so that case-insensitive match is performed for SQL commands and case-sesitive match is performed for everything else.
This issue is related to version 16.
How to verify this?
This issue is related to version 16.
How to verify this?
> This issue is related to version 16. How to verify this?
If I remember correctly, the implementation of FS SQL auto-completion is incomplete and yet to be reviewed/refactored, and that's why we push FS SQL auto-completion related issues to ADS version 16. You probably do not have to worry about this issue at the moment.
> This issue is related to version 16. How to verify this?
If I remember correctly, the implementation of FS SQL auto-completion is incomplete and yet to be reviewed/refactored, and that's why we push FS SQL auto-completion related issues to ADS version 16. You probably do not have to worry about this issue at the moment.
Issue #8080 |
| New |
Completion |
| No due date |
| Fixed Build trunk/30666 |
| No time estimate |
I am not familiar with auto-completion related code. I traced the code and it seems to me FS auto-completion popup does not have any DB server related information; hence, to handle your test case, I made change so that the match-comparison performed in the popup is case-insensitive (it seems to me this is the way how match-comparison is implemented in the Query Analyzer's auto-completion popup). SVN r30651.