David W. Van Couvering wrote: > > Is there any reason why the message text isn't sent over ahead of time > as part of the original exception message sent from the server? I > don't see the value in saving network traffic when you are in an > exception path. Is it because many exceptions get ignored/handled > without being reported to the user? Anybody know the > history/motivation behind this?
The stored procedure error message model causes all sorts of troubles. Eliminating the need for that would be a meaty, high value DRDA project for someone with interest. Of course we would need to make sure the old clients still work. There are a few serious problems in the DRDA protocol and/or Derby that I know of related to this and probably more if you were to look into it deeper. A few issues off the top of my head .. 1) There is limited length* *message info sent to the client. JCC and DerbyClient cheat a bit. ODBC does not. 2) There is no communication of client locale but we could work around that with an EXCSQLSET. 3) There are issues returning multiple exceptions to the client. I think in SQLAM level 7 some things were improved. If interested look for SQLCAXGRP in the DRDA manual. The info is really spread out. Kathey
