You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a cross-issue between VSCode - code for i and the Db2 for i extensions and mapepire.
When creating procedures and functions in VScode, and a syntax or semantic error is typed in, it would be appreciated if the cursor could be positioned on the code line and column where the error exists.
This requires that mapepire has the possibility to query this information.
This information can be obtained with GET DIAGNOSTIC and retrieve the DB2_OFFSET value.
This can be done in run() method "catch" of the ClientRequest module, and return the offset along with the JSON error object along with the sql_state and sql_rc
Alternatively - it could be a separate method getDiagnostics() that Db2 for i (or any other client) could call - perhaps also for other diagnostics info in the future
The feature might also be useful when entering any other complex SQL statements ( that fails)
ACS SQL already has this feature (to some extent)
The text was updated successfully, but these errors were encountered:
This is a cross-issue between VSCode - code for i and the Db2 for i extensions and mapepire.
When creating procedures and functions in VScode, and a syntax or semantic error is typed in, it would be appreciated if the cursor could be positioned on the code line and column where the error exists.
The requirement for Db2 for i is posted here:
codefori/vscode-db2i#309
This requires that mapepire has the possibility to query this information.
This information can be obtained with GET DIAGNOSTIC and retrieve the DB2_OFFSET value.
This can be done in run() method "catch" of the ClientRequest module, and return the offset along with the JSON error object along with the sql_state and sql_rc
Alternatively - it could be a separate method getDiagnostics() that Db2 for i (or any other client) could call - perhaps also for other diagnostics info in the future
The feature might also be useful when entering any other complex SQL statements ( that fails)
ACS SQL already has this feature (to some extent)
The text was updated successfully, but these errors were encountered: