> I would like to have the problem with the getErrorCode in SQLException > always returning 0 fixed. So I figured, why don't do it myself? ... Just tot > check before I start looking at it... > > Has there been any attempt fixing it? Are someone doing it anyway? Are there > any known problems with doing it?
This issue is not unrelated to the fact that the server doesn't provide any error codes in the first place, so the JDBC driver will have a hard time guessing them. Fixing this is in the (my) agenda; it may or may not happen for the next major release.