> There must have been a regression somewhere, as I don't remember any change
> which would break the MySQL support, so I think it's accidental and we may
> be able continue supporting MySQL (through the MySQL-specific store).
> Hopefully we can find the cause of this problem.
>
> Remy
It looks quite deliberate. The code which creates temporary actions,
permissions, etc. for initial database population runs fine the first
time. However, when starting up a second time, these already exist. As a
result, an exception is thrown and the transaction aborted. Since the
transaction abort doesn't DO anything with mysql, the temporary
actions/permissions don't get removed, so there's basically zero
security.
Michael
