Database authority allocation system and method

Abstract

The present invention discloses a database authority allocation system and method, the method comprising the following steps: pre-allocating database authority levels for users, and opening corresponding data to users based on the authority levels; obtaining the levels corresponding to all data in the user's historical access data; obtaining the access time of all data in the user's historical records; obtaining the number of accesses to all data in the user's historical records; and determining the user's actual authority level based on the access time and number of data of different levels in the user's historical access data. The database authority allocation method provided by the present invention determines the user's actual authority level based on the data browsed by the user in the past period of time, so that the data opened in the database can be better matched with the user. In the above embodiment, the method adopted does not require manual determination of the user's database level, and is more efficient.

Description

Technical Field

[0001] The present invention belongs to the technical field of data allocation and processing, and in particular relates to a database authority allocation system and method. Background Art

[0002] In the process of opening data in the database to designated groups, it is easy for the data level to not match the user, which makes it difficult for the user to accept the information in the database. In the past, it was mainly through manual confirmation, based on the subjective consciousness of the operator, to open different levels of data to different users, but this method is inefficient and is still prone to errors such as mismatch between the open data level and the user. Summary of the invention

[0003] The present invention provides a database authority allocation system and method, which can effectively improve data allocation efficiency and effectively avoid errors caused by mismatch between open data levels and users.

[0004] The present invention is achieved through the following technical solutions:

[0005] On the one hand, the present invention provides a method for allocating database permissions, comprising the following steps: pre-allocating database permission levels for users, and opening corresponding data to users based on the permission levels; obtaining the levels corresponding to all data in the user's historical access data; obtaining the access time of all data in the user's historical records; obtaining the number of accesses to all data in the user's historical records; and determining the user's actual permission level based on the access time and number of data of different levels in the user's historical access data.

[0006] In some embodiments, determining the actual permission level of a user based on the access time and number of times of data of different levels in the user's historical access data includes the following steps:

[0007] Get the user's browsing value:

[0008]

[0009] Wherein, a is the first preset constant, is the time to access the m-th level data, b is the second preset constant, is the number of times the mth level data is accessed; c is a third preset constant, wherein the third preset constant has different values ​​based on different levels of data; the user's browsing value is compared with multiple preset threshold ranges; based on the threshold range in which the user's browsing value falls, the actual authority level corresponding to the threshold range is obtained.

[0010] In some of the embodiments, before determining the actual authority level of the user based on the information of the time, number of times and level of the user's access data, the following steps are also included: obtaining the validity of the user's access data; and determining the actual authority level of the user based on the valid access data.

[0011] In some of the embodiments, obtaining the validity of user access data includes the following steps: dividing the data accessed by the user into multiple segments; determining whether the user is browsing the data of any segment for the first time after browsing the data of the segment; when it is determined that the user is browsing the data of the segment for the first time, continuing to determine whether the user has browsed the data of the previous and most recent segment before the segment data within a first preset time period; if it is determined that the user has browsed the data of the previous and most recent segment before the segment data within the first preset time period, then the data access of the segment is valid.

[0012] In some of the embodiments, after determining whether the user is browsing the data of the segment for the first time, the following steps are also included: if it is determined that the user is not browsing the data of the segment for the first time, continue to determine whether the user has browsed the data of the previous and most recent segment before the segment data within a second preset time period; if the user has browsed the data of the previous and most recent segment before the segment data within the second preset time period, then the data access to the segment is valid.

[0013] In some embodiments, based on the information of the time, number of times and level of the user's access to data, determining the actual permission level of the user includes the following steps: obtaining the browsing value of the user:

[0014]

[0015] Wherein, a is the first preset constant, is the time to access the mth level valid data, b is the second preset constant, is the number of times the mth level valid data is accessed, e is the fourth preset constant, is the time to access the mth level invalid data, f is the fifth preset constant, is the number of times the mth level of invalid data is accessed, wherein e<a, f<b; c is a third preset constant, wherein the third preset constant has different values ​​based on data of different levels; the user's browsing value is compared with multiple preset threshold ranges; based on the threshold range in which the user's browsing accuracy value falls, the actual authority level corresponding to the threshold range is obtained.

[0016] In some of the embodiments, after determining the actual authority level of the user, the following steps are also included: after a preset time period, re-obtaining the levels corresponding to all data in the user's historical access data; and obtaining the access time and access count of all data in the user's historical records; and re-determining the user's actual authority level based on the access time and access count of different levels in the re-obtained user's historical access data.

[0017] In some of the embodiments, after determining the actual authority level of the user based on information about the time, number of times and level of the user's data access, the following steps are also included: based on the user's actual authority level, assigning thresholds for the time, number of times and / or level of data access corresponding to the user.

[0018] In some of the embodiments, after determining the actual authority level of the user based on the access time and number of data of different levels in the user's historical access data, the following steps are also included: determining whether the actual authority level of the user is the same as the pre-allocated authority level; when it is determined that the actual authority level of the user is not the same as the pre-allocated authority level, issuing a first prompt message.

[0019] In some of the embodiments, after determining whether the actual authority level of the user is the same as the pre-allocated authority level, the following steps are also included: when it is determined that the actual authority level of the user is not the same as the pre-allocated authority level, determining whether there is a level jump between the actual authority level of the user and the pre-allocated authority level; when it is determined that there is a level jump between the actual authority level of the user and the pre-allocated authority level, issuing a second prompt message.

[0020] On the other hand, an embodiment of the present application provides a database permission allocation system, including a memory and a processor, wherein a computer program is stored in the memory, and the processor executes the computer program to implement any of the database permission allocation methods in the above embodiments.

[0021] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0022] The database authority allocation method provided by the present invention determines the actual authority level of the user based on the data browsed by the user in the past period of time, so that the data opened in the database can be better matched with the user. In the above embodiment, the method adopted does not require manual determination of the user's database level, which is more efficient and will not cause the situation where the database open data level does not match the user again due to manual misjudgment. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 A schematic diagram of a flow chart of a method for allocating database permissions provided in some embodiments of the present invention;

[0025] Figure 2 A flowchart of the step of determining the actual authority level of a user in the database authority allocation method provided in some embodiments of the present invention. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments.

[0027] In the description of the present invention, it should be noted that the terms "center", "up", "down", "left", "right", "vertical", "horizontal", "inside", "outside", etc. used to indicate the orientation or position relationship are based on the orientation or position relationship shown in the accompanying drawings, or are the orientation or position relationship commonly placed when the product of the invention is used. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention.

[0028] In addition, if the terms "horizontal" or "vertical" appear in the description of the present invention, it does not mean that the components are required to be absolutely horizontal or suspended, but can be slightly tilted. For example, "horizontal" only means that its direction is more horizontal than "vertical", and does not mean that the structure must be completely horizontal, but can be slightly tilted.

[0029] In the description of the present invention, it is also necessary to explain that, unless otherwise clearly specified and limited, the terms "set", "install", "connect", and "connect" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0030] The terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the listed steps or modules, but may optionally include steps or modules that are not listed, or may optionally include other steps or modules that are inherent to these processes, methods, products, or devices.

[0031] On the one hand, the present application embodiment provides a method for allocating database permissions. Figure 1 , mainly including the following steps:

[0032] S10, pre-allocate database permission levels for users, and open corresponding data to users based on their permission levels. In step S10, in the process of pre-allocating database permission levels for users, in some examples, it is possible to manually pre-allocate database permission levels for all users based on the experience of the operator; in other examples, it is also possible to pre-allocate the same permission level to all users, such as all initial users are given a first-level permission level. After pre-allocating database permission levels for users, the database can open all data of the corresponding level according to the user's pre-allocated level.

[0033] S20, obtain the level corresponding to all data in the user's historical access data. In step S20, in the process of the user using the database, obtain the level corresponding to the data accessed by the user in the past period of time in the process. Different authority levels correspond to different data. For example, when the user's authority level is 1, all the data that can be obtained are first-level data; when the user's authority level is 2, all the data that can be obtained except the first-level data are second-level data. In the user's historical access data, due to the subjectivity of the user, at least part of the data of any level will be accessed in the past period of time.

[0034] S30, continue to obtain the access time of all data in the user history record. In step S30, the access time of all data in the history record refers to the time taken to browse data of different levels. When the user obtains data of multiple levels, the time taken to access data of different levels is respectively.

[0035] S40, continue to obtain the number of accesses to all data in the user history records. Similarly, in step S30, the number of accesses to all data in the history records refers to the number of times data of different levels are browsed. Exemplarily, each time a user opens a database to close the database can be counted as one time, or each time a user opens a database within a period of time can be counted as one time. For example, in units of days, if the user has opened the database on that day, it can be considered that the user has opened it once. After each database opening, if the user browses the primary data, the secondary data, and the tertiary data during that time, it is considered that the user has browsed the primary data once, the secondary data once, and the tertiary data once, respectively.

[0036] S50: Determine the actual authority level of the user based on the access time and number of times of data of different levels in the user's historical access data.

[0037] In the above embodiment, historical access data refers to specific data accessed in the past period of time, and historical records refer to the record of the time and number of times the user accessed the corresponding data. Based on the data browsed by the user in the past period of time, the actual authority level of the user is determined so that the data opened in the database can be better matched with the user. In the above embodiment, the method adopted does not require manual determination of the user's database level, which is more efficient and will not cause the situation where the database open data level does not match the user again due to manual misjudgment.

[0038] In some of these examples, see Figure 2 In step S50, based on the access time and number of different levels of data in the user's historical access data, determining the user's actual authority level mainly includes the following steps:

[0039] S501, obtaining the user's browsing value:

[0040]

[0041] The browsing value S refers to the relevant progress of the user browsing the data set. By using an intelligent algorithm to directly determine the user's browsing progress on the data set, it is used to assist in determining the allocation of the user's database authority level, avoiding the errors that may be caused by manual allocation, and on the other hand, it also improves the overall efficiency. Wherein, a is the first preset constant, ( ) is the time to access the m-th level data, b is the second preset constant, is the number of times the m-th level data is accessed; c is a third preset constant, wherein the third preset constant has different values ​​based on different levels of data.

[0042] In step S501, the first preset constant and the second preset constant can be set according to specific circumstances, and the third preset constant corresponds to data of different levels, and data of different levels correspond to different values. These values ​​pre-exist in the database and only need to be directly called.

[0043] In some examples, the first preset constant, the second preset constant and the third preset constant are pre-set; then, the user automatically obtains data of multiple levels in the past period of time, and the specific browsing value of the user can be obtained based on the above formula according to the access time and the number of accesses of each level of data. The length of the past period of time can also be specifically set according to the actual situation. On the other hand, in the process of multiple user database authority allocations, the first preset constant, the second preset constant, the third preset constant and the length of the past period of time can also be adjusted at any time.

[0044] In some examples, the third preset constant may be set to have a larger value as the permission level of the data increases.

[0045] In other examples, it can be determined based on the time or number of times the user accesses the data of the corresponding level. For example, if the user accesses the data of the first level, the second level and the third level, and the time or number of times the user accesses the second level is the largest, then the third preset constant corresponding to the second level can use the maximum value. In this example, multiple third preset constants are stored in the database, and then the values ​​of the constants are called one by one according to the situation.

[0046] S502, comparing the user's browsing value with multiple preset threshold ranges. In step S502, multiple preset threshold ranges are pre-set in the database, each threshold range corresponds to an actual permission level, and by comparison, it can be determined which actual permission level the user's browsing value better matches.

[0047] S503: Based on the threshold range within which the browsing value of the user falls, obtain the actual permission level corresponding to the threshold range.

[0048] In the above embodiment, the process of how to use the access time and number of times of data of different levels in the user's historical access data to specifically determine which actual permission level the user is more matched with is specifically described.

[0049] In some embodiments, based on the information of the time, number of times and level of the user's access to the data, before determining the actual permission level of the user, the following steps are also included:

[0050] K10, obtaining the validity of user access data. In K10, when obtaining the validity of user access data, in some examples, any segment of data is used as the judgment object. Among all the data obtained by the user, the data will be segmented in advance. When the user completely browses the segment of data, it is considered that the user has accessed the segment of data, and then further judged whether the access to the data is valid.

[0051] K20. Determine the actual authority level of the user based on the valid access data. In K20, the subsequent steps of determining the actual authority level of the user are performed based on the valid access data.

[0052] In the above embodiment, the data accessed by the user is distinguished to obtain valid browsing data and invalid browsing data, and then the subsequent step of determining the actual authority level of the user is performed based on the valid browsing data. Through this embodiment, the data browsed by the user can be split, the browsing situation of the user can be further determined, and a more accurate actual authority level can be assigned to the user.

[0053] In some embodiments, in step K10, obtaining the validity of user access data mainly includes the following steps:

[0054] K101, divide the data accessed by the user into multiple segments. In step K101, the segment where the data accessed by the user is located can be divided according to the rules for dividing the data of a permission level in the database. For example, the data of a permission level is divided into 10 segments in total. When the user completely browses one of the segments, it is considered that the user has accessed the segment.

[0055] K102. After the user browses the data of any section, it is determined whether it is the first time for the user to browse the data of the section. In step K102, it can be determined by means of database memory whether it is the first time for the user to browse the data of the section.

[0056] K103. When it is determined that the user is browsing the data of the segment for the first time, continue to determine whether the user has browsed the data of the segment before and most recently in the first preset time period. In step K103, it is determined whether the user has acquired the data of the segment before and most recently in the segment before browsing the data of the segment, and whether the acquisition time is within the first preset time. If there is no data of other segments before the data browsed by the user, no determination is required, and the data of the segment is directly considered to be valid data.

[0057] K104. If it is determined that the user has browsed the data of the previous and most recent segment of the segment data within the first preset time period, then the data access of the segment is valid.

[0058] In the above embodiment, by judging whether the user adopts the association to obtain relevant data, it can be judged whether the user has a good grasp of the acquired data, and then based on the grasp, it is judged whether the browsed data is valid, thereby further determining the user's browsing situation and assigning the user a more accurate actual authority level.

[0059] In some embodiments, in step K102, after determining whether the user browses the data of the segment for the first time, the following steps are further included:

[0060] K105. If it is determined that the user is not browsing the data of the segment for the first time, continue to determine whether the user has browsed the data of the segment before and most recently in the second preset time period. In step K105, the second preset time period is usually set to be longer than the first preset time period, that is, when the user is not browsing the data of the segment for the first time, the user's requirements for the associated browsing of the data of the segment will be lower.

[0061] K106. If the user browses the data of the previous and most recent segment of the segment data within the second preset time period, the data access of the segment is valid.

[0062] In the above embodiment, steps K105 and K106 are a whole and are arranged in parallel with step K104, so there is no order relationship. Through the configuration of the above embodiment, the validity of the data browsed by the user can be further determined, thereby further determining the browsing status of the user and allocating a more accurate actual authority level to the user.

[0063] In some embodiments, in step S50, based on the information of the time, number of times and level of the user's access to data, determining the actual permission level of the user includes the following steps:

[0064] S501-1. Obtaining the user's browsing value:

[0065]

[0066] Wherein, a is the first preset constant, is the time to access the mth level valid data, b is the second preset constant, is the number of times the mth level valid data is accessed, e is the fourth preset constant, is the time to access the mth level invalid data, f is the fifth preset constant, is the number of times the m-th level invalid data is accessed, wherein e<a, f<b; c is a third preset constant, wherein the third preset constant has different values ​​based on different levels of data.

[0067] In step S501-1, e and f can be 0. In some examples, when the database is small or each level has less data, e and f can be set to non-zero and smaller values ​​as appropriate; and when the database is large and each level has more data, e and f can be 0.

[0068] In some examples, the first preset constant, the second preset constant, the third preset constant, the fourth preset constant and the fifth preset constant can be preset in advance; then the user can automatically obtain the data of multiple levels and the validity of the access data in the past period of time, and the specific browsing value of the user can be obtained based on the above formula according to the access time and the number of accesses to each level of data. The length of the past period of time can also be set according to the actual situation. On the other hand, in the process of multiple user database authority allocations, the first preset constant, the second preset constant, the third preset constant and the length of the past period of time can also be adjusted at any time.

[0069] S502-1, comparing the user's browsing value with multiple preset threshold ranges;

[0070] S503-1. Based on the threshold range within which the browsing accuracy value of the user falls, obtain the actual permission level corresponding to the threshold range.

[0071] In the above embodiment, a more accurate browsing value is obtained by judging whether the data access is valid.

[0072] In some embodiments, after determining the actual permission level of the user based on the information of the time, number of times and level of the user's access to the data in step S50, the following steps are also included:

[0073] After a preset time period, the levels corresponding to all data in the user's historical access data are obtained again; and the access time and access count of all data in the user's historical records are obtained; and based on the access time and access count of different levels in the re-obtained user's historical access data, the user's actual authority level is determined again.

[0074] Through the configuration of the above embodiment, after the actual authority level of the user is determined, the step of determining the authority level can still be repeated during the subsequent use of the database, and the actual authority level of the user last time is used as the pre-allocated authority level to continue updating the actual authority level of the user.

[0075] In some embodiments, after determining the actual permission level of the user based on the information of the time, number of times and level of the user's access to the data in step S50, the following steps are also included:

[0076] T10. Based on the actual authority level of the user, assign a threshold value of time, number of times and / or level for the user to access the corresponding data.

[0077] In the above embodiment, based on the actual authority level of the user, while the user is given the authority to open the corresponding data in a conventional manner, at least one threshold value of the time, number of times and level for the user to access the data of each level is set again. The threshold value can be a maximum value or a minimum value, which can be determined specifically according to the actual situation. In some examples, when the minimum value threshold is set, as the authority level of the user's database increases, the user needs to have a higher grasp of the data in the database, so the browsing value required by the user is also higher.

[0078] In some embodiments, after determining the actual permission level of the user based on the access time and number of accesses to data of different levels in the user's historical access data in step S50, the following steps are also included:

[0079] S60: Determine whether the actual authority level of the user is the same as the pre-allocated authority level. In step S60, after determining the actual authority level of the user, the actual authority level may be the same as the pre-allocated authority level, or may be different.

[0080] S70: When it is determined that the actual authority level of the user is different from the pre-allocated authority level, a first prompt message is issued.

[0081] In the above embodiment, when the user's database authority level changes compared to the pre-assigned authority level, a first prompt message may be issued, which may be used for recording or for secondary judgment to determine whether the user's level change is appropriate.

[0082] In some embodiments, when the database permission level of the newly assigned user changes compared to the pre-assigned permission level, the user can be pre-assigned a permission level with a lower permission level between the two to ensure the security of the data in the database. After the first prompt message is issued, the administrator makes a judgment and confirms whether to adjust the permission level of the user again.

[0083] In some embodiments, after step S60: determining whether the actual permission level of the user is the same as the pre-assigned permission level, the following steps are further included:

[0084] S80: When it is determined that the actual authority level of the user is different from the pre-allocated authority level, continue to determine whether there is a level-jumping phenomenon between the actual authority level of the user and the pre-allocated authority level. In step S80, the level-jumping phenomenon means that the actual authority level of the user differs from the pre-allocated level by two levels or more, and may have continuously decreased by at least two levels, or may have continuously increased by at least two levels.

[0085] S90: Based on step S80, when it is determined that the user's actual authority level and the pre-assigned authority level are beyond the level, a second prompt message is issued. In step S90, the issued second prompt message can be used for recording or sent to an operator as an early warning message, and then the operator manually determines whether the situation is abnormal.

[0086] In the above embodiment, abnormal information is obtained by measuring the actual authority level of the user for subsequent judgment.

[0087] On the other hand, an embodiment of the present application provides a database permission allocation system, including a memory and a processor, wherein a computer program is stored in the memory, and the processor executes the computer program to implement any of the database permission allocation methods in the above embodiments.

[0088] In some of the embodiments, a subsystem may be set up in an existing database management system. The subsystem corresponds to the relevant content of the database authority allocation system of the present application, executes the database authority allocation method, and is connected to the existing database management system. When sending corresponding data, the data sent by the subsystem is sent to the existing database management system. When the database management system sends data, the subsystem can be executed directly.

[0089] In some other embodiments, the database authority allocation system of the present application may also be run as an independent system.

[0090] This embodiment further provides a computer storage medium on which a computer program is stored. The computer program is loaded by the processing module to implement any of the database authority allocation methods in the above embodiments.

[0091] The above description is only a preferred embodiment of the present invention and does not constitute any limitation to the present invention. Any simple modification or equivalent changes made to the above embodiments based on the technical essence of the present invention shall fall within the protection scope of the present invention.

Claims

1. A method for allocating database permissions, characterized in that: The following steps are involved: Pre-assign database permission levels to users, and open corresponding data to users based on permission levels; Get the levels corresponding to all data in the user's historical access data; Get the access time of all data in the user's history; Get the number of visits to all data in the user's history; Based on the access time and number of different levels of data in the user's historical access data, the user's actual permission level is determined, including: Get the user's browsing value; Comparing the user's browsing value with a plurality of preset threshold ranges; Based on the threshold range within which the user's browsing value falls, the actual permission level corresponding to the threshold range is obtained; Based on the information of the time, number of times and level of the user's access to the data, before determining the user's actual permission level, the following steps are also included: Obtain the validity of user access data; Determine the user's actual permission level based on valid access data; Obtaining the validity of user access data includes the following steps: Divide the data accessed by users into multiple segments; After the user browses the data of any segment, it is determined whether the user browses the data of the segment for the first time; When it is determined that the user browses the data of the segment for the first time, continue to determine whether the user browses the data of the segment before and most recently in the first preset time period; If it is determined that the user has browsed the data of the previous and most recent segment of the segment data within the first preset time period, the data access of the segment is valid; Based on the information about the time, number of times and level of the user's access to the data, determining the user's actual permission level includes the following steps: Get the user's browsing value: Wherein, a is the first preset constant, is the time to access the mth level valid data, b is the second preset constant, is the number of times the mth level valid data is accessed, e is the fourth preset constant, is the time to access the mth level invalid data, f is the fifth preset constant, is the number of times the invalid data of the mth level is accessed, wherein e<a, f<b; c is a third preset constant, wherein the third preset constant is a different value based on data of different levels; Comparing the user's browsing value with a plurality of preset threshold ranges; Based on the threshold range within which the browsing accuracy value of the user falls, the actual permission level corresponding to the threshold range is obtained.

2. The database authority allocation method according to claim 1, characterized in that: After determining whether the user browses the data of the segment for the first time, the following steps are also included: If it is determined that the user is not browsing the data of the segment for the first time, continue to determine whether the user has browsed the data of the previous and most recent segment of the data of the segment within a second preset time period; If the user browses the data of the previous and most recent segment of the segment data within the second preset time period, the data access of the segment is valid.

3. The database authority allocation method according to claim 1, characterized in that: After determining the user's actual permission level, the following steps are also included: After a preset time period, the levels corresponding to all data in the user's historical access data are obtained again; and the access time and access count of all data in the user's historical records are obtained; And based on the access time and number of different levels in the user's historical access data obtained again, the user's actual authority level is determined again.

4. The database authority allocation method according to claim 1, characterized in that: After determining the user's actual permission level based on the information of the time, number of times and level of the user's access to the data, the following steps are also included: Based on the actual authority level of the user, a threshold value of time, number of times and / or level of access to data corresponding to the user is assigned.

5. The database authority allocation method according to claim 1, characterized in that: After determining the actual permission level of the user based on the access time and number of times of data of different levels in the user's historical access data, the following steps are also included: Determine whether the user's actual permission level is the same as the pre-assigned permission level; When it is determined that the actual authority level of the user is different from the pre-assigned authority level, a first prompt message is issued.

6. The database authority allocation method according to claim 5, characterized in that: After determining whether the user's actual permission level is the same as the pre-assigned permission level, the following steps are also included: When it is determined that the actual authority level of the user is different from the pre-assigned authority level, it is determined whether there is a level-override phenomenon between the actual authority level of the user and the pre-assigned authority level; When it is determined that the user's actual authority level exceeds the pre-assigned authority level, a second prompt message is issued.

7. A database authority allocation system, characterized in that: It comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the database authority allocation method according to any one of claims 1 to 6.

Images