django cms 3.1.x Documentationproved not to be fast enough for big tree operations (>1000 pages); tree corruption, because of transactional errors, has also been a problem. django-treebeard uses MP (Materialized Path). MP is more efficient0 码力 | 200 页 | 1.63 MB | 1 年前3
django cms 3.3.x Documentationproved not to be fast enough for big tree operations (>1000 pages); tree corruption, because of transactional errors, has also been a problem. django-treebeard uses MP (Materialised Path). MP is more efficient0 码力 | 386 页 | 1.56 MB | 1 年前3- Django 2.1.x Documentationwill need to set this; in general, however, you should be developing your own projects against a transactional database and be using TestCase for most tests, and thus not need this setting. The initial serialization in the server configuration. MySQL’s default storage engine is InnoDB. This engine is fully transactional and supports foreign key references. It’s the recommended choice. However, the InnoDB autoincrement be able to access the project. A bank website, however, most likely doesn’t want to allow any transactional pages to be linked from external sites so the 'Strict' flag would be appropriate. • 'Lax' (default):0 码力 | 1910 页 | 6.49 MB | 1 年前3
- Django 2.1.x Documentationwill need to set this; in general, however, you should be developing your own projects against a transactional database and be using TestCase for most tests, and thus not need this setting. The initial serialization in the server configuration. MySQL’s default storage engine is InnoDB. This engine is fully transactional and supports foreign key references. It’s the recommended choice. However, the InnoDB autoincrement be able to access the project. A bank website, however, most likely doesn’t want to allow any transactional pages to be linked from external sites so the 'Strict' flag would be appropriate. 'Lax' (default):0 码力 | 2790 页 | 2.71 MB | 1 年前3
- Django 2.2.x Documentationneed to set this; in general, however, you should be developing your own projects against a transactional database and be using TestCase for most tests, and thus not need this setting. The initial serialization in the server configuration. MySQL’s default storage engine is InnoDB. This engine is fully transactional and supports foreign key references. It’s the recommended choice. However, the InnoDB autoincrement be able to access the project. A bank website, however, most likely doesn’t want to allow any transactional pages to be linked from external sites so the 'Strict' flag would be appropriate. 'Lax' (default):0 码力 | 2915 页 | 2.83 MB | 1 年前3
- django cms 3.4.x Documentationproved not to be fast enough for big tree operations (>1000 pages); tree corruption, because of transactional errors, has also been a problem. django-treebeard uses MP (Materialised Path). MP is more efficient0 码力 | 395 页 | 1.64 MB | 1 年前3
- django cms 3.6.x Documentationproved not to be fast enough for big tree operations (>1000 pages); tree corruption, because of transactional errors, has also been a problem. django-treebeard uses MP (Materialised Path). MP is more efficient0 码力 | 278 页 | 1.63 MB | 1 年前3
- django cms 3.10.x Documentationproved not to be fast enough for big tree operations (>1000 pages); tree corruption, because of transactional errors, has also been a problem. django-treebeard uses MP (Materialised Path). MP is more efficient0 码力 | 296 页 | 1.79 MB | 1 年前3
- django cms 3.5.x Documentationproved not to be fast enough for big tree operations (>1000 pages); tree corruption, because of transactional errors, has also been a problem. django-treebeard uses MP (Materialised Path). MP is more efficient0 码力 | 403 页 | 1.69 MB | 1 年前3
- django cms 3.7.x Documentationproved not to be fast enough for big tree operations (>1000 pages); tree corruption, because of transactional errors, has also been a problem. django-treebeard uses MP (Materialised Path). MP is more efficient0 码力 | 409 页 | 1.67 MB | 1 年前3
共 45 条
- 1
- 2
- 3
- 4
- 5