[MySQL] Some non-transactional changed tables couldn ' t be rolled back

Source: Internet
Author: User

When using peewee transactions, a depressed problem is encountered and the transaction seems to be invalid!

This simplifies the model, writes a simple test code, and discovers the problem, as shown in title.

Find answers to:

https://github.com/etianen/django-reversion/issues/362

Https://dev.mysql.com/doc/refman/5.0/en/nontransactional-tables.html

The reason is that the database table engine needs to be set to InnoDB to support things, and the workaround is as follows:

Http://dev.mysql.com/doc/refman/5.6/en/converting-tables-to-innodb.html

That is, the engine that will need to support the things table is set to Innodb,sql as follows:

ALTER TABLE my_table ENGINE=INNODB;

[MySQL] Some non-transactional changed tables couldn ' t be rolled back

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.