On 11/2/07, paha <[EMAIL PROTECTED]> wrote:
> Correct, but i would like to get from provider original localized messages
> for standard exceptions like concurrency to identify the exception itself,
> not to show it direct to user ;-) . It is not perfect, and must be avoided
> in any way, but if it happened, how can i know what exceptions should be
> thrown (or actions taken) if i get rows with different RowErrors and no real
> exception thrown - i can only compare RowErrors with standard Exception
> messages :) and here i fail, because message for DBConcurrencyException
> thrown from provider is not standard and doesn't coincide with default
> message for this case.
Hmm, but in row.RowError can be almost any message from any exception.
So we will have dictionary for a lot of texts. And this is IMO no good
way. I know, that with ContinueUpdateOnError the handling is harder,
but solving this in provider doesn't look like good design to me.
--
Jiri {x2} Cincura (Microsoft Student Partner)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
