[MDEV-30852] 'Error message' improvement request(include 'call stack') Created: 2023-03-14  Updated: 2023-10-07  Resolved: 2023-10-07

Status: Closed
Project: MariaDB Server
Component/s: None
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Mitchell Lee Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None


 Description   

Hi.
Below situation, only shows final error message that just 'Unknown column xxxx' or 'dead lock xxxx'

--------
Procedure_1
> calls Procedure_1_1
> calls Procedure_1_1_1
> calls Procedure_1_1_2
> calls Procedure_1_1_3
> calls Procedure_1_1_4
> calls Procedure_1_1_5
> calls Procedure_1_1_5_1
> calls Procedure_1_1_5_2
> calls Procedure_1_1_5_3
> calls Procedure_1_1_5_4 * here
> calls Procedure_1_1_5_5
> calls Procedure_1_1_5_6
> calls Procedure_1_1_6
> calls Procedure_1_2
> calls Procedure_1_3
> calls Procedure_1_4
> calls Procedure_1_5
> calls Procedure_1_6

With this,
if we got an error in the 'Procedure_1_1_5_6',
then no way to identify the location of the error.
Just say. 'deadlock'. or 'unknown column xxx'
Pain to find the error location. need to improve asap.

 Comments   
Comment by Sergei Golubchik [ 2023-05-01 ]

did you try SHOW WARNINGS immediately after the error?

Comment by Mitchell Lee [ 2023-05-02 ]

I'm not talking about the `manual` operation,
but automated call like EVENT or expternal script as python.
Which no room and not working the `show xxxx` stuff.
In these days, no sql stuff in manual environment but automated environment.

Comment by Sergei Golubchik [ 2023-05-30 ]

you still can run show warnings from your python script.
As far as event is concerned, you cannot see the output anyway, so a call stack woldn't have helped much.

Generated at Thu Feb 08 10:19:23 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.