Phpcms Why should I dedicate a table to the "Audit" status of an article?

Article Table news has a field status, why do you want to make another table, the audit status of the article copied to this audit table, directly modify the article table is not the same status field?

News 12 is the field status

    1   id    mediumint(8)        UNSIGNED        2    catid    smallint(5)        UNSIGNED        3    typeid    smallint(5)        UNSIGNED        4    title    varchar(200)    utf8_general_ci            5    style    char(24)    utf8_general_ci            6    thumb    varchar(100)    utf8_general_ci            7    keywords    varchar(80)    utf8_general_ci            8    description    mediumtext    utf8_general_ci            9    posids    tinyint(1)        UNSIGNED        10    url    char(100)    utf8_general_ci            11    listorder    tinyint(3)        UNSIGNED        12    status    tinyint(2)        UNSIGNED        13    sysadd    tinyint(1)        UNSIGNED        14    islink    tinyint(1)        UNSIGNED        15    username    char(20)    utf8_general_ci            16    inputtime    int(10)        UNSIGNED        17    updatetime    int(10)        UNSIGNED    

Content_check 7 for field status

    1   checkid    char(15)    utf8_general_ci    2    catid    smallint(5)        UNSIGNED        3    siteid    smallint(5)        UNSIGNED        4    title    char(80)    utf8_general_ci            5    username    char(20)    utf8_general_ci            6    inputtime    int(10)        UNSIGNED        7    status    tinyint(1)    

Reply content:

Article Table news has a field status, why do you want to make another table, the audit status of the article copied to this audit table, directly modify the article table is not the same status field?

News 12 is the field status

    1   id    mediumint(8)        UNSIGNED        2    catid    smallint(5)        UNSIGNED        3    typeid    smallint(5)        UNSIGNED        4    title    varchar(200)    utf8_general_ci            5    style    char(24)    utf8_general_ci            6    thumb    varchar(100)    utf8_general_ci            7    keywords    varchar(80)    utf8_general_ci            8    description    mediumtext    utf8_general_ci            9    posids    tinyint(1)        UNSIGNED        10    url    char(100)    utf8_general_ci            11    listorder    tinyint(3)        UNSIGNED        12    status    tinyint(2)        UNSIGNED        13    sysadd    tinyint(1)        UNSIGNED        14    islink    tinyint(1)        UNSIGNED        15    username    char(20)    utf8_general_ci            16    inputtime    int(10)        UNSIGNED        17    updatetime    int(10)        UNSIGNED    

Content_check 7 for field status

    1   checkid    char(15)    utf8_general_ci    2    catid    smallint(5)        UNSIGNED        3    siteid    smallint(5)        UNSIGNED        4    title    char(80)    utf8_general_ci            5    username    char(20)    utf8_general_ci            6    inputtime    int(10)        UNSIGNED        7    status    tinyint(1)    

The number of articles to be audited is certainly not large, but the article table may have a lot of articles, even need to sub-table.

Looking at the table structure alone is not very meaningful, I have not used phpcms, I think this may be to make it easier to expand the audit mechanism development.
For example, a publication using PHPCMS to publish electronic version, according to the process, the copy to go through the team leader, deputy editor, editor three audit, for similar cases:
First of all, from the authority control, the right management after the table is more clear, the audit permission does not include the original text modification, while avoiding the editing of the manuscript contaminated the audited data.
Second, the reviewer can comment on the content, because it is a copy of the content, so it does not affect the original text.
Finally, the table has a separate status field, which can extend the review process such as first instance, review, and grievance.
Add, some CMS will be the draft is also independent storage, in fact, there is no particular good and bad problem, I think it is related to the character of the designer. Some people like to focus on the problem, after the Yimapingchuan, some people like to spread the problem, to avoid the complexity of the stack to reduce the control of project development progress. It's like an audit table. Instead of creating a separate table, you can actually accomplish a predetermined task, that is, the logic of the program is much more complex.

