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
If we go to any index in the left pane object viewer and click on ALTER INDEX, it returns a weird 'not found ' error.
Can you let us know if you can repro it and I tested with latest 20.5 -> 22.0 GA. Same issue.
Tested and confirmed that unsetting public.reserved_keywords='' does resolve the issue and ADS DDL extraction generates HG index creation stmt while with reserved_keywords='limit' it didn't do this on the same table.
Reference private case #288
By default, the limit keyword is usually turned off. In the case where it is turned on, our query is not identifying limit as a keyword and is getting a syntax error.
SET OPTION PUBLIC.RESERVED_KEYWORDS = 'LIMIT'
This fix needs to be forward fitted into 22.1 and tested. Patch is attached.
This fix needs to be forward fitted into 22.1 and tested. Patch is attached.
Hi Tom,
I tested the patch and added a commit At revision: 58960
Thanks,
Vishav
Hi Tom,
I tested the patch and added a commit At revision: 58960
Thanks,
Vishav
Thanks Vishav... Please demonstrate your unit test cases so that the QA team understands how this should be tested.
Thanks Vishav... Please demonstrate your unit test cases so that the QA team understands how this should be tested.
QA Verified issue: Sybase IQ (native connection) from ADS22 (even ADS20.5) fails on ALTER INDEX with index not found error
and its working fine and as expected
OS - Windows 8.1, Ubuntu, Mac
Build - dev-17-no-ofsc/
Test Rail link :
Windows: ADS 22.1 Test Suite (Windows) - TestRail
QA Verified issue: Sybase IQ (native connection) from ADS22 (even ADS20.5) fails on ALTER INDEX with index not found error
and its working fine and as expected
OS - Windows 8.1, Ubuntu, Mac
Build - dev-17-no-ofsc/
Test Rail link :
Windows: ADS 22.1 Test Suite (Windows) - TestRail
Issue #15858 |
| Verified |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
By default, the limit keyword is usually turned off. In the case where it is turned on, our query is not identifying limit as a keyword and is getting a syntax error.
SET OPTION PUBLIC.RESERVED_KEYWORDS = 'LIMIT'