| List: | MySQL++ | « Previous MessageNext Message » | |
| From: | Jonathan Wakely | Date: | June 13 2009 10:29am |
| Subject: | Re: Why dynamic allocation for Option objects? | ||
| View as plain text | |||
2009/6/12 Kevin Regan:
> I was taking another look at this issue (please see the code below to following along
> with my issue). If the DBDriver::set_option returns non-empty error string, wouldn't
> it have deleted the objected contained in o that Connection::set_option will call
> typeid(*o) on?
Yes, that's a bug.