So, we could analyze a stack trace (somewhere in SQL engine) and prepare
more detailed top message.
>From my point of view it should not be too hard.
Vasiliy, please create issue in JIRA for that.
May be one day it will be fixed :)
On Fri, Nov 18, 2016 at 5:50 PM, Sergi Vladykin
wrote:
> All we
All we can do here is to propagate error message from H2. Probably it will
give more details.
Sergi
2016-11-18 13:31 GMT+03:00 Alexey Kuznetsov :
> Vasiliy, Pavel.
>
> I think it is a usability issue.
> Not always user has a full stack trace.
> For example, if I execute this query via some UI to
Vasiliy, Pavel.
I think it is a usability issue.
Not always user has a full stack trace.
For example, if I execute this query via some UI tool - in most cases I
will see only top level message.
I have no idea how hard to implement such functionality.
Sergi (as a most expert in SQL engine) could
Vasiliy, did you examine the full stack trace?
I've tried an invalid query and got the following in one of the inner
exceptions:
Caused by: org.h2.jdbc.JdbcSQLException: Table "ORGANIZATION2" not found
However, I agree that this should be present in the top level exception
message.
On Fri, Nov 1
