1,801
การแก้ไข
ผลต่างระหว่างรุ่นของ "CuneiForm"
ล
→With Database Commit
| บรรทัดที่ 826: | บรรทัดที่ 826: | ||
* '''form''' ''(FlaskForm-CuneiForm)'': The form to read the committing data from. | * '''form''' ''(FlaskForm-CuneiForm)'': The form to read the committing data from. | ||
* '''perm_bit''' ''(int)'': The integer permission bit. This form of permission control is quite rigid and works well with single-table databases. | * '''perm_bit''' ''(int)'': The integer permission bit. This form of permission control is quite rigid and works well with single-table databases. | ||
* '''allowed_action''' ''( | * '''allowed_action''' ''({{code|lang=python|{'add':<bool>, 'edit':<bool>, 'delete':<bool>} }})'': A more complicated form of permission control. This allows for more precise control. However, it cannot be read directly from a permission database, but must be interpreted from the stored integer value upon use. | ||
* '''suppress_success_msg''' ''(bool)'': Whether to show a message on action success. | * '''suppress_success_msg''' ''(bool)'': Whether to show a message on action success. | ||
* '''lock_on_add''' ''(bool)'': Lock the document upon successful add-type commit. (This works for multi-table databases by putting the current username in the '''editting''' column of the header table.) | * '''lock_on_add''' ''(bool)'': Lock the document upon successful add-type commit. (This works for multi-table databases by putting the current username in the '''editting''' column of the header table.) | ||