Unhide Zend_Exception in UtilityComponent::run_sql_from_file

[bbenoist]

With this PR, error messages are way clearer than current Unable to connect:

FYI, the error displayed here is because the MySQL instance I used had NO_ZERO_DATE enabled...

[jamiesnape]

Is your example in development or production mode? In production, it should not give this information.

[bbenoist]

@jamiesnape Development mode as I am still struggling with making Midas to connect to an instance of the official MySQL Docker image.

I agree that such information might be sensible for production.

However:

• this specific function is called for administration-only operations (AFAIK).
• only displaying Unable to connect is not enough to determine the actual cause of an issue.

[mgrauer]

I agree it would be good to see the actual exception, but I don't think we want to display this in the web app.

How about you log the exception like this and continue to pass the existing message?