Warren Young wrote:
> Warren Young wrote:
>> You're right, though, that a problem would occur if the second
>> select_db() call threw an exception.
> Turns out, this is extremely unlikely to occur. For it to happen,
> create_db() -- which doesn't throw exceptions -- would have to succeed,
> and then select_db() on the newly created database would have to fail. I
> wouldn't be surprised if MySQL's security is fine-grained enough that
> you could make a user that can create databases but not be able to
> select them, but why would someone do such a thing?
> I've withdrawn that change because it breaks the ABI, pointlessly.
Hmm. In the instance I was toying with, the db already existed from a
previous run, and I was using the default user, who didn't have
permission with the database, so that's exactly what was happening in my
runs of resetdb. So not extremely unlikely, tho that is perhaps a pretty