mtassinari Posted July 30, 2010 Share Posted July 30, 2010 Hi everybodyI'm opening this thread to make a "feature request" if possible: I always find hard to understand my reports' problems when there is an exception thrown at compile time, especially when it comes to SQL errors.The usual message I get is "error executing statement for ***", and that alone isn't much help in identifying the cause of the problem. Wouldn't it be possible, in this specific case, to add the full SQL error message, and more in general to have more self-explaining excepion messages? Link to comment Share on other sites More sharing options...
lucianc Posted August 9, 2010 Share Posted August 9, 2010 The SQLException is nested inside the JRException as a cause. If you print the full stacktrace of the exception, you should see the SQLException exception message.Other than that, I don't know how JR would be able to tell more about an SQL error raised during a query execution.Regards,Lucian Link to comment Share on other sites More sharing options...
mtassinari Posted August 10, 2010 Author Share Posted August 10, 2010 well, for example the SQL exception should contain at least the error number and error message reported from MySQL. Anyway, I'll give it a look to see if I missed it, perhaps it is already there and I simply did not check the entire stack. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now