--- "Jeroen T. Vermeulen" <[EMAIL PROTECTED]> wrote:
> I think there are two different issues here, really:
> one is knowing
> exactly which exceptions can come out of a library
> function, and the other
> is getting more information from the exception.
>
> The first can always use a bit more documentation,
> though I don't think
> it'll ever get to the point where we can say exactly
> what exceptions may
> be thrown from any function. At least not without a
> serious risk of
> getting it wrong.
>
> The second I hope is largely addressed by the
> expanded exception
> hierarchy. If you need more specific exception
> classes based on
> particular SQL error codes, just let us know (or
> submit a patch) and we
> can arrange that with the framework that is now in
> place.
This is very helpful, and the second method
addresses most of my problems. I would still plea to
increase documentation of what pqxx_exceptions are
thrown where. Even a generic "this method might throw
pqxx_exception or its children" would be a useful
improvement, but I agree that incorrect documentation
is worse than not doing it at all.
Thanks again,
Gary
____________________________________________________________________________________Building
a website is a piece of cake. Yahoo! Small Business gives you all the tools to
get online.
http://smallbusiness.yahoo.com/webhosting
_______________________________________________
Libpqxx-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
