Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
0.9.0-RC1 addition:
When running SQL statements that terminate with an exception, it is difficult to determine what specific SQL statement has lead to the exception. While calling code can somewhat reason about it, it would make sense to attach the offending SQL statement to the actual exception.
Introduce a final String sql field and getSql method to R2dbcException that can be nullable. Retrofit R2dbcBadGrammarException.offendingSql to remove the field and redirect getOffendingSql() to R2dbcException.getSql().