> After various changes in the last month or so, it's no longer even
> slightly possible to use slide's JDBC stores with a
> non-transaction-capable database (previously it was, though it did
> sometimes cause problems).
>
> This makes mysql pretty useless - but we still have stores specifically
> designed to work around mysql's lack of proper transactions, as well as
> examples which suggest using mysql. (yes, I'm aware that very recent
> versions of mysql sort of have limited transaction capabilities, but
> they have other limitations too)
>
> If you all agree that trying to make slide work without transactions is
> a poinless exercise, it'd probably be a good idea to excise at least the
> mysql-specific stores, since those explicitly ignore the errors caused
> by not having real transactions.
>
> Comments?
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
