Hi Eric
On 23/03/2010, at 4:39 AM, Eric Day wrote:
My suggestion would be to:
* Not allow custom exceptions. There may be a possible exception for
some plugins which require them if they are based on other libraries
that use them, but this should be discouraged.
* Never allow exceptions to propagate across module boundaries.
* Catch string/STL exceptions as close as possible to the source and
translate those into return codes. This allows calling methods to
do the correct thing, whether it be abort a query, abort a session,
or halt the entire server.
OQGRAPH uses/needs them with BGL.
It's local to the engine, doesn't cross module boundaries or up above
the engine.
I think 2&3 make sense, probably 1 also.
Cheers,
Arjen.
--
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Exceptional Services for MySQL at a fixed budget.
Follow our blog at http://openquery.com/blog/
OurDelta: packages for MySQL and MariaDB @ http://ourdelta.org
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
