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 | Major |
| Complexity | Unknown |
| Component | Stored Procedure Debugger |
| Version | 16.0 |
|
|
127 KB
|
|
97 KB
|
|
126 KB
|
|
75 KB
Issue observed in Sybase Anywhere 16 also. It was working fine on 15.0.0-dev-58
It seems that this issue surfaced between 15.0.0-dev-65 and 15.0.0-dev-66. Specifically, SVN r35448 with the comment "<aquadatastudio: 10227> init work for RedShift support". Re-assigning to @ivangron to take a look.
Note that clicking compile again generates an error message. See attached.
It seems that this issue surfaced between 15.0.0-dev-65 and 15.0.0-dev-66. Specifically, SVN r35448 with the comment "<aquadatastudio: 10227> init work for RedShift support". Re-assigning to @ivangron to take a look.
Note that clicking compile again generates an error message. See attached.
The schema was not getting set on create, it was only been set on alter. This impacts all databases all versions.
The schema was not getting set on create, it was only been set on alter. This impacts all databases all versions.
We need to fix this for v15 as well. @ivan: once you fix it let me know and I will go through full round of testing all the databases
We need to fix this for v15 as well. @ivan: once you fix it let me know and I will go through full round of testing all the databases
I have reopened the issue and moved to version 15 and have back ported the code fixes to 15. checking in code and resolving issue...
I have reopened the issue and moved to version 15 and have back ported the code fixes to 15. checking in code and resolving issue...
Issue #12366 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
Issue observed in Sybase Anywhere 16 also. It was working fine on 15.0.0-dev-58