Is there a way to identify and handle database errors (such as a table or database not existing)? Currently it seems like the plugin is just putting the error into the msg.payload and then passing it along like a normal message, but I don't want to display the errors (which includes the SQL that caused the error) to the users.
Is there a way to identify and handle database errors (such as a table or database not existing)? Currently it seems like the plugin is just putting the error into the msg.payload and then passing it along like a normal message, but I don't want to display the errors (which includes the SQL that caused the error) to the users.