Easily find issues by searching: #<Issue ID>
Example: #1832
| Dev | pradipjare(*) |
| QA |
|
| Priority | Minor |
| Complexity | Unknown |
| Component | DB - jtds |
| Version | 17.0 |
The Arithmetic Overflow Warning thrown by SQL Server does not provide line number or error description in Aqua Data Studio whereas it does in SQL Server Management Studio. Would there be a way to incorporate better information regarding this warning in ADS to improve debugging focus?
|
|
29 KB
|
|
76 KB
|
|
184 KB
| Field | Old Value | New Value |
|---|---|---|
| Dev Assignee | Unassigned | NielsGron (Niels Gron) |
| QA Assignee | Unassigned | SachinPrakash (Sachin Prakash) |
| Version | 14.0 | 15.0 |
Executing this :
select 1, 1/0
go
select 1, 2
select 1, 1/0
go
Gives results of this :
>[Error] Script lines: 1-2 --------------------------
Divide by zero error encountered.
Msg: 8134, Level: 16, State: 1, Procedure: , Line: 1
[Executed: 4/29/2014 10:37:08 AM] [Execution: 1ms]
>[Error] Script lines: 3-6 --------------------------
Divide by zero error encountered.
[Executed: 4/29/2014 10:37:08 AM] [Execution: 1ms]
Looks like the jTDS JDBC driver is not returning the line number for some queries. We will need to trace the jTDS source code.
| Field | Old Value | New Value |
|---|---|---|
| Dev Assignee | NielsGron (Niels Gron) | SachinPrakash (Sachin Prakash) |
| QA Assignee | SachinPrakash (Sachin Prakash) | NielsGron (Niels Gron) |
Where this is problematic for me is when the warning gets thrown when a stored procedure execution completes. I have no way of knowing where the warning was encountered during execution.
Where this is problematic for me is when the warning gets thrown when a stored procedure execution completes. I have no way of knowing where the warning was encountered during execution.
| Field | Old Value | New Value |
|---|---|---|
| Dev Assignee | SachinPrakash (Sachin Prakash) | JohnLH (John LH) |
| Field | Old Value | New Value |
|---|---|---|
| Dev Assignee | JohnLH (John LH) | vikramrc (Vikram Roopchand) |
| Field | Old Value | New Value |
|---|---|---|
| Version | 15.0 | Future - 0.1 |
| Field | Old Value | New Value |
|---|---|---|
| Version | Future - 0.1 | 15.0 |
| Field | Old Value | New Value |
|---|---|---|
| Version | 15.0 | 16.0 |
| Field | Old Value | New Value |
|---|---|---|
| Version | 16.0 | Future - 0.1 |
| Field | Old Value | New Value |
|---|---|---|
| Version | Future - 0.1 | 17.0 |
| Field | Old Value | New Value |
|---|---|---|
| Component | Editor | App - General |
| Field | Old Value | New Value |
|---|---|---|
| QA Assignee | NielsGron (Niels Gron) | tomconrad (Thomas Conrad) |
| Field | Old Value | New Value |
|---|---|---|
| Component | App - General | DB - jtds |
| Field | Old Value | New Value |
|---|---|---|
| Version | 17.0 | 18.0 |
| Field | Old Value | New Value |
|---|---|---|
| Dev Assignee | vikramrc (Vikram Roopchand) | pradipjare(*) (Pradip Jare) |
| Field | Old Value | New Value |
|---|---|---|
| QA Assignee | tomconrad (Thomas Conrad) | vikramrc (Vikram Roopchand) |
| Field | Old Value | New Value |
|---|---|---|
| Fixed Build | SVN r#4439 | |
| Resolution | Fixed | |
| Resolved Date | Oct 16, 2015 9:55 AM | |
| Status | New | Resolved |
SVN r#4439 (Pune v18 ADS component branch) :
Showing line number in error message.Fixed.
SVN r#4439 (Pune v18 ADS component branch) :
Showing line number in error message.Fixed.
| Field | Old Value | New Value |
|---|---|---|
| Status | Resolved | Verified |
Verified in ADS- 18.0.dev-13. Refer updated screenshot '11981-ADS-18-dev-13.png' file
Verified in ADS- 18.0.dev-13. Refer updated screenshot '11981-ADS-18-dev-13.png' file
I have created new directory for jtds code,called as aqua-jtds in the Pune v18 ADS component branch.Added all source code from GitHub , Also made necessary changes to show the line number in error message and checked-in with SVN r#8056(Pune v18 ADS component branch) .
Also checked-in newly changed jtds jars in to the Pune v18 trunk with SVN r#8080
I have created new directory for jtds code,called as aqua-jtds in the Pune v18 ADS component branch.Added all source code from GitHub , Also made necessary changes to show the line number in error message and checked-in with SVN r#8056(Pune v18 ADS component branch) .
Also checked-in newly changed jtds jars in to the Pune v18 trunk with SVN r#8080
| Field | Old Value | New Value |
|---|---|---|
| Fixed Build | SVN r#4439 | SVN r#8056 |
| Status | Verified | Resolved |
| Field | Old Value | New Value |
|---|---|---|
| QA Assignee | vikramrc (Vikram Roopchand) | tariqrahiman (Tariq Rahiman) |
| Fixed Build | SVN r#8056 | devi-144, SVN r#8056 |
| Field | Old Value | New Value |
|---|---|---|
| Status | Resolved | Verified |
Verified in ADS- 18.0.dev-146. Refer updated screenshot 'Updated11981-ADS-18-dev-146.png' file
Verified in ADS- 18.0.dev-146. Refer updated screenshot 'Updated11981-ADS-18-dev-146.png' file
| Field | Old Value | New Value |
|---|---|---|
| Resolution | Fixed | Incomplete |
| Resolved Date | Oct 16, 2015 9:55 AM | |
| Status | Verified | Reopened |
| Field | Old Value | New Value |
|---|---|---|
| Version | 18.0 | 17.0 |
This fix caused the following issue:
Execute the below SQL:
DECLARE @COUNT INT = 0 WHILE(@COUNT < 5) BEGIN print(@COUNT) SET @COUNT = @COUNT + 1 END
After the fix, the output is as shown below. This output is incorrect.
======
Command was executed successfully
Warnings: --->
W (1): Id 0, Level 0, State 1, Line 5
0
W (2): Id 0, Level 0, State 1, Line 5
1
W (3): Id 0, Level 0, State 1, Line 5
2
W (4): Id 0, Level 0, State 1, Line 5
3
W (5): Id 0, Level 0, State 1, Line 5
4
<---
[Executed: 9/20/2016 9:12:48 AM] [Execution: 9s]
======
Prior to the fix, the output was as shown below. This is the correct output.
Command was executed successfully
Warnings: --->
W (1): 0
W (2): 1
W (3): 2
W (4): 3
W (5): 4
<---
[Executed: 9/20/2016 8:50:29 AM] [Execution: 14ms]
This fix caused the following issue:
Execute the below SQL:
DECLARE @COUNT INT = 0 WHILE(@COUNT < 5) BEGIN print(@COUNT) SET @COUNT = @COUNT + 1 END
After the fix, the output is as shown below. This output is incorrect.
======
Command was executed successfully
Warnings: --->
W (1): Id 0, Level 0, State 1, Line 5
0
W (2): Id 0, Level 0, State 1, Line 5
1
W (3): Id 0, Level 0, State 1, Line 5
2
W (4): Id 0, Level 0, State 1, Line 5
3
W (5): Id 0, Level 0, State 1, Line 5
4
<---
[Executed: 9/20/2016 9:12:48 AM] [Execution: 9s]
======
Prior to the fix, the output was as shown below. This is the correct output.
Command was executed successfully
Warnings: --->
W (1): 0
W (2): 1
W (3): 2
W (4): 3
W (5): 4
<---
[Executed: 9/20/2016 8:50:29 AM] [Execution: 14ms]
| Field | Old Value | New Value |
|---|---|---|
| Fixed Build | devi-144, SVN r#8056 | 17.0.8-7, devi-144, SVN r#8056 |
| Resolution | Incomplete | Fixed |
| Resolved Date | Sep 20, 2016 7:24 PM | |
| Status | Reopened | Resolved |
| Field | Old Value | New Value |
|---|---|---|
| Status | Resolved | Verified |
| Field | Old Value | New Value |
|---|---|---|
| Status | Verified | Closed |
Verified in ADS v18.0.0-devi-240 with the jtds Driver and output are the same now. Both issues are now resolved.
Verified in ADS v18.0.0-devi-240 with the jtds Driver and output are the same now. Both issues are now resolved.
Issue #11981 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 17.0.8-7, devi-144, SVN r#8056 |
| No time estimate |
Executing this :
select 1, 1/0
go
select 1, 2
select 1, 1/0
go
Gives results of this :
>[Error] Script lines: 1-2 --------------------------
Divide by zero error encountered.
Msg: 8134, Level: 16, State: 1, Procedure: , Line: 1
[Executed: 4/29/2014 10:37:08 AM] [Execution: 1ms]
>[Error] Script lines: 3-6 --------------------------
Divide by zero error encountered.
[Executed: 4/29/2014 10:37:08 AM] [Execution: 1ms]
Looks like the jTDS JDBC driver is not returning the line number for some queries. We will need to trace the jTDS source code.