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 | Editor - Debugger for Sybase |
| Version | 12.0 |
Sybase debugger : "Debugger Query Window" fails on any query execution. See attached screenshot.
alpha-8 - works
alpha-9 - does not work
alpha-10 - does not work
alpha-12 - does not work
alpha-15 - does not work
SVN # 28572-28579 -
|
|
116 KB
This bug is caused by SVN #28575, where we changed the default fetchsize. ConnectionWrapper will set the fetchsize for all Statements, and we also do the same in AFScriptContext.Line2267. If we open a Debugger Query Window and execute a statement, it will execute the statement with the SybaseDebugger.createStatement() object which doesn't set the fetch size, but then does in AFScriptContext.
The bug seems to be in the jConnect driver, but I am not sure why the driver is failing when executing the CallableStatement if and only if the fetchsize is set on the statement.
Looks like this bug has always existed in the jConnect driver, but no one ran into it because no one has ever change the default fetch size and used the Sybase debugger on the connection. This is not triggered with ADS 12 which always sets a fetchsize. I've added a workaround for the jConnect bug by disabling Sybase fetchsize changes on PreparedStatements. This means that the Debugger Query Window will always have the jConnect fetchsize default. Fixed in SVN #30671
Looks like this bug has always existed in the jConnect driver, but no one ran into it because no one has ever change the default fetch size and used the Sybase debugger on the connection. This is not triggered with ADS 12 which always sets a fetchsize. I've added a workaround for the jConnect bug by disabling Sybase fetchsize changes on PreparedStatements. This means that the Debugger Query Window will always have the jConnect fetchsize default. Fixed in SVN #30671
Issue #8101 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 12.0.14 |
| No time estimate |
This bug is caused by SVN #28575, where we changed the default fetchsize. ConnectionWrapper will set the fetchsize for all Statements, and we also do the same in AFScriptContext.Line2267. If we open a Debugger Query Window and execute a statement, it will execute the statement with the SybaseDebugger.createStatement() object which doesn't set the fetch size, but then does in AFScriptContext.
The bug seems to be in the jConnect driver, but I am not sure why the driver is failing when executing the CallableStatement if and only if the fetchsize is set on the statement.