I have some issues concerning the use of exceptions in the MySQL++ library:
When you have exceptions_ = false in Result and you do:
Result a = query.store();
a.disable_exceptions(); // Exceptions disabled...
Result b = a;
Then exceptions are enabled again in 'b'. I understand people might want
to work with exceptions, but is this not a flaw in the design? If a has
exceptions disabled, I would expect b to have them disabled too...
If you have a connections where the exceptions are disabled, and you
create a query and stuff... And then you store (like the example above),
the Result you get back have exceptions enabled again... Which is a
little unlogical as well...