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
It would be useful if the PDO wrapper handled DB errors more verbosely (in debug mode).
I recently had a situation where an error generated in a stored function called from a trigger gave me an error message along the lines of:
{'code': '500', 'msg': 'Table Rubrix.op does not exist'}
Here, op was the table's alias in the query executed in the stored function, so it didn't help at all. It would have saved me a lot of time to have the PDO wrapper give me a stack trace for that error. I'm not sure if that is possible, but at the least we should be able to add the fact that the error was originally generated from a trigger and the name of the trigger.
The text was updated successfully, but these errors were encountered:
It would be useful if the PDO wrapper handled DB errors more verbosely (in debug mode).
I recently had a situation where an error generated in a stored function called from a trigger gave me an error message along the lines of:
Here,
op
was the table's alias in the query executed in the stored function, so it didn't help at all. It would have saved me a lot of time to have the PDO wrapper give me a stack trace for that error. I'm not sure if that is possible, but at the least we should be able to add the fact that the error was originally generated from a trigger and the name of the trigger.The text was updated successfully, but these errors were encountered: