A method, system, device, and medium for reverse storage of field permissions.

Abstract

This disclosure relates to a method, system, device, and medium for reverse storage of field permissions. The method includes the following steps: acquiring field permission data; filtering out authorized field permission data from the field permission data to retain unauthorized field permission data; performing an inversion operation on the unauthorized field permission data to obtain reverse-stored field permission data; and storing the reverse-stored field permission data. In the field permission acquisition and authentication stage, the reverse definition of the full-field authorization permission status is used to achieve authentication with less permission data. This disclosure reduces the required storage data through permission inversion; and reduces system computation and achieves fast authentication by using the inverted field permissions and a dynamic table field set.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of field authority storage, in particular to a reverse storage method, system, device and medium for field authority. BACKGROUND

[0002] At present, the existing field authority system stores authorized field authorities. When the number of roles, forms and fields is large, a large amount of authority data needs to be stored and high authentication operations are required. With the emergence of zero-code applications, dynamic forms make the use of field authorities more complex, and field authorities need to be synchronized in real time with the increase and decrease of dynamic form fields. The application of multi-role authority also increases the data and operation amount of field authorities.

[0003] The existing mainstream technical solution (or the closest technical solution) currently has the following disadvantages / deficiencies:

[0004] 1. Large amount of stored data, occupying a large amount of storage space

[0005] 2. Large data volume consumes more system operations.

[0006] 3. In zero-code applications, field authorities need to be synchronized in real time. SUMMARY

[0007] The present disclosure provides a reverse storage method, system, device and medium for field authority, which can solve the problems of the existing field authority system, such as large amount of stored data, occupying a large amount of storage space, reducing system operations, improving the speed of authority identification, and the need for real-time synchronization of increased field authorities. To solve the above technical problems, the present disclosure provides the following technical solutions:

[0008] As one aspect of an embodiment of the present disclosure, a reverse storage method for field authority is provided, comprising the following steps:

[0009] Obtaining field authority data;

[0010] Filtering out the authorized field authority data in the field authority data to retain unauthorized field authority data;

[0011] Performing a NOT operation on the unauthorized field authority data to obtain reverse storage field authority data;

[0012] Storing the reverse storage field authority data.

[0013] Optionally, before obtaining the field authority data, the following step is further included: defining a reverse storage structure for field authority, the reverse storage structure including one or more of the following parameters: field ID, table ID, non-readable authority, non-writable authority, non-deletable authority.

[0014] Optionally, the dynamic table and view are acquired at the same time as the field permission data, and the dynamic table and view are directly stored without the need for the NOT operation.

[0015] Optionally, the reverse storage of the field permission data further comprises the following steps before the storage: determining whether there is reverse field permission data, and if there is reverse field permission data, merging the acquired dynamic table permission, view permission and the reverse storage of the field permission data to obtain a final field permission set; and if there is no field permission data, merging the dynamic table and view permission, the dynamic table permission, the view permission and the field permission to obtain a final field permission set.

[0016] Optionally, after the final field permission set is acquired, the following step is further included: acquiring the dynamic table and view field set to obtain all field sets that need to be output.

[0017] Optionally, after all field sets that need to be output are acquired, the following step is further included: performing permission authentication on the dynamic table, view field set and the final field permission set, and filtering out an effective field set through intersection calculation.

[0018] Optionally, after the effective field set is filtered out, the following step is further included: outputting the effective field set.

[0019] As another aspect of the embodiments of the present disclosure, a reverse storage system of field permission is provided, comprising:

[0020] a field permission acquisition module that acquires field permission data;

[0021] an authorized field filtering module that filters out authorized field permission data in the field permission data to retain unauthorized field permission data;

[0022] a NOT operation module that performs a NOT operation on the unauthorized field permission data to obtain reverse storage of the field permission data;

[0023] a reverse storage module that stores the reverse storage of the field permission data.

[0024] As another aspect of the embodiments of the present disclosure, an electronic device is provided, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the reverse storage method of field permission when executing the computer program.

[0025] As another aspect of the embodiments of the present disclosure, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program, and the program is executed by a processor to implement the reverse storage method of field permission.

[0026] Compared with the prior art, the present disclosure has the following beneficial effects:

[0027] 1. In the storage phase of the field authority, the required storage data is reduced by the authority negation operation; meanwhile, in the increase and decrease of the dynamic form field, the field authority no longer needs to be synchronized, reducing the data communication and the occupied storage space.

[0028] 2. In the field authority acquisition and authentication phase, the field authority after the negation operation can quickly authenticate with the dynamic table field set. BRIEF DESCRIPTION OF DRAWINGS

[0029] Figure 1 Flow chart for the reverse storage method of the field authority in Example 1;

[0030] Figure 2 Flow chart for defining and storing the reverse field authority in Example 1;

[0031] Figure 3 Application flow chart for the reverse storage of the field authority in Example 1;

[0032] Figure 4 Schematic block diagram of the reverse storage system of the field authority in Example 2. DETAILED DESCRIPTION

[0033] Various exemplary embodiments, features, and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numbers in the drawings represent the same or similar elements. Although various aspects of the embodiments are shown in the drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

[0034] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations.

[0035] The term "and / or" used herein only means an association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can mean that A exists alone, A and B exist together, and B exists alone. In addition, the term "at least one" herein means any one of the plurality or any combination of at least two of the plurality, for example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0036] In addition, in order to better illustrate the present disclosure, numerous specific details are given in the specific embodiments below. Those skilled in the art should understand that the present disclosure can also be implemented without some specific details. In some examples, methods, means, elements, and circuits that are well known to those skilled in the art are not described in detail in order to highlight the main idea of the present disclosure.

[0037] It can be understood that the above-mentioned various method embodiments mentioned in the present disclosure can be combined with each other to form combined embodiments without deviating from the principle logic. Due to the limited space, the present disclosure will not be repeated.

[0038] In addition, the present disclosure also provides a reverse storage method, system, device and medium of field authority, which can be used to implement any of the reverse storage methods of field authority provided by the present disclosure. The corresponding technical solutions and descriptions are described in the method part and are not repeated.

[0039] The execution subject of the reverse storage method of field authority can be a computer or other devices capable of realizing the oil tank multi-path gas detection device. For example, the method can be executed by a terminal device or a server or other processing device, wherein the terminal device can be a user equipment (User Equipment, UE), a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. In some possible implementation manners, the reverse storage method of field authority can be realized by calling the computer readable instructions stored in the memory by the processor.

[0040] Embodiment 1

[0041] The present embodiment provides a reverse storage method of field authority, as shown in Figure 1 The present embodiment provides a reverse storage method of field authority, as shown in

[0042] S10, obtaining field authority data;

[0043] S20, filtering out authorized field authority data in the field authority data to retain unauthorized field authority data;

[0044] S30, performing a NOT operation on the unauthorized field authority data to obtain reverse storage field authority data;

[0045] S40, storing the reverse storage field authority data.

[0046] Based on the above steps, the present embodiment constructs a reverse storage method of field authority. By filtering out authorized field authority data in the field authority data to retain unauthorized field authority data, performing a NOT operation on the unauthorized field authority data to obtain reverse storage field authority data, and storing the reverse storage field authority data, the storage data is reduced. In the field authority acquisition and identification stage, the reverse definition of the full field authorization authority state is used to achieve fast authentication with less authority data and reduce system operation.

[0047] The steps of the embodiments of the present disclosure are described in detail as follows. Figure 2 , Figure 3

[0048] S10, acquire field permission data;

[0049] The dynamic table, view, and field permission data are set or submitted by the user to the permission system.

[0050] Before acquiring the field permission data, the following steps are further included: defining a field permission reverse storage structure, which includes one or more of the following parameters: field ID, table ID, non-readable permission, non-writable permission, and non-deletable permission.

[0051] S20, filter out authorized field permission data in the field permission data to retain unauthorized field permission data;

[0052] Filtering out authorized field permission and retaining unauthorized field permission can effectively reduce the field data that needs to be stored.

[0053] S30, performing a NOT operation on the unauthorized field permission data to obtain reverse storage field permission data;

[0054] By traversing the field permission and performing a NOT operation on the unauthorized field permission, reverse storage field permission data is obtained. Through the permission NOT operation, the required storage data is reduced, and in the addition and deletion of dynamic table fields, there is no longer a need to synchronize the field permission, reducing data communication and storage space occupation.

[0055] S301, before storing the reverse field permission data, the following steps are further included: determining whether there is reverse storage field permission data, if there is reverse storage field permission data, merging the simultaneously acquired dynamic table permission, view permission, and the reverse field permission data as a final field permission set; if there is no field permission data, merging the dynamic table and view permission as full field authorized permission with the dynamic table permission, view permission, and field permission as a final field permission set.

[0056] S302, after acquiring the final field permission set, the following steps are further included: acquiring a dynamic table and view field set to acquire all field sets that need to be output.

[0057] S303, after acquiring all field sets that need to be output, the following steps are further included: performing permission authentication on the dynamic table, view field set, and final field permission set, and filtering out an effective field set through intersection calculation.

[0058] S304, after filtering out the effective field set, the following steps are further included: outputting the effective field set to the terminal.

[0059] ​S40, store the reverse storage field permission data.

[0060] Only store the data after the unauthorized field permission is negated, and do not store when there is no data. The dynamic table and view permission data do not need to be negated and can be directly stored in the conventional manner.

[0061] Using the negation method and storing only the unauthorized field, the amount of stored data can be reduced, and the storage space occupied can be reduced. Using the reverse definition of the full field authorization permission state, authentication can be implemented with less permission data. After using reverse field permission storage, when adding or deleting fields in a dynamic form in zero code application, real-time synchronization of field permissions is not required, saving a large amount of data storage and data transmission.

[0062] As a preferred embodiment, the reverse storage method of the field permission can be applied in the Mingdao cloud zero code, including the following steps:

[0063] Define the reverse storage structure of the worksheet field permission, define the worksheet permission, view permission storage structure;

[0064] Set the application role worksheet permission, view permission, field permission;

[0065] Filter out the authorized field permission data in the field permission data and retain the unauthorized field permission data;

[0066] The permission service stores the worksheet permission and the view permission;

[0067] Iterate through the field permission, negate the unauthorized field permission, and store the unauthorized field permission to the database;

[0068] The permission service obtains the worksheet permission, view permission, and reverse stored field permission from the database, calculates the final field permission, and presents the authorized field set after authentication.

[0069] Embodiment 2

[0070] As another aspect of the embodiments of the present disclosure, a reverse storage system 100 of field permission is also provided, as shown in the following steps: Figure 4

[0071] The field permission acquisition module 1 acquires the field permission data;

[0072] The authorized field filtering module 2 filters out the authorized field permission data in the field permission data to retain the unauthorized field permission data;

[0073] The negation operation module 3 negates the unauthorized field permission data to obtain the reverse storage field permission data; ​

[0074] The reverse storage module 4 stores the reverse storage field permission data.

[0075] Based on the above modules, the embodiment of the present disclosure constructs a reverse storage method of field permission. The authorized field permission data in the field permission data is filtered out to retain the unauthorized field permission data. The unauthorized field permission data is subjected to a NOT operation to obtain reverse storage field permission data. The reverse storage field permission data is stored, thereby reducing the storage data. In the field permission acquisition and identification stage, the reverse definition of the full field authorization permission state is used to quickly authenticate with less permission data, reduce system operation, and realize the reverse storage system 100 of field permission.

[0076] The various modules of the embodiment of the present disclosure will be described in detail below.

[0077] The field permission acquisition module 1

[0078] The dynamic table, view, and field permission data are set or submitted by the user to the permission system.

[0079] Before acquiring the field permission data, the following steps are further included: defining a reverse storage structure of field permission, the reverse storage structure including one or more of the following parameters: field ID, table ID, non-readable permission, non-writable permission, and non-deletable permission.

[0080] The authorized field filtering module 2

[0081] The authorized field permission in the field permission data is filtered out to retain the unauthorized field permission, which can effectively reduce the field data that needs to be stored.

[0082] The NOT operation module 3

[0083] The unauthorized field permission data is subjected to a NOT operation to obtain reverse storage field permission data.

[0084] The unauthorized field permission data is subjected to a NOT operation to obtain reverse storage field permission data. Through the permission NOT operation, the required storage data is reduced, and in the increase and decrease of the fields of the dynamic table, the field permission no longer needs to be synchronized, thereby reducing the data communication and reducing the storage space.

[0085] Before storing the reverse field permission data, the following steps are further included: judging whether there is reverse storage field permission data. If there is reverse storage field permission data, the dynamic table permission and the view permission obtained at the same time are merged with the reverse field permission data as the final field permission set. If there is no field permission data, the dynamic table and view permission are merged with the dynamic table permission, the view permission, and the field permission as the full field authorization permission and the final field permission set.

[0086] S302, after obtaining the final field permission set, further comprising the following steps: obtaining a dynamic table and view field set to obtain all field sets that need to be output.

[0087] S303, after obtaining all field sets that need to be output, further comprising the following steps: performing permission authentication on the dynamic table, view field set and the final field permission set, and screening out an effective field set through intersection calculation.

[0088] S304, after screening out the effective field set, further comprising outputting the effective field set to a terminal.

[0089] Reverse storage module 4

[0090] Store the reverse storage field permission data.

[0091] In some embodiments, the above system 100 is used in the following way in use:

[0092] S1: Run the field permission acquisition module 1. The dynamic table, view, and field permission data are set or submitted by the user to the permission system;

[0093] S2: Run the authorized field filtering module 2. Filter out the authorized field permissions in the field permission data, and keep the unauthorized field permissions;

[0094] S3: Run the negation operation module 3. Traverse the field permissions, and perform negation operation on the unauthorized field permissions to obtain reverse storage field permission data;

[0095] S4: Reverse storage module 4. Store the reverse storage field permission data.

[0096] Based on the description of the above embodiments, the embodiments of the present disclosure can achieve the following technical effects:

[0097] 1) In the storage stage of the field permission, the required storage data is reduced through the permission negation operation; at the same time, in the increase and decrease of the dynamic form field, the field permission no longer needs to be synchronized, reducing data communication and reducing storage space occupation.

[0098] 2) In the field permission acquisition and authentication stage, the field permission after the negation operation can quickly authenticate with the dynamic table field set.

[0099] After using the reverse field permission storage, when the dynamic form of the zero-code application increases or decreases the field, it does not need to synchronize the field permission in real time, saving a lot of data storage and data transmission.

[0100] Embodiment 3

[0101] An electronic device includes a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the reverse storage method of field permissions in Embodiment 1 when executing the computer program.

[0102] Embodiment 3 of the present disclosure is merely an example and should not bring any limitation to the function and use range of the embodiments of the present disclosure.

[0103] The electronic device can be in the form of a general computing device, for example, it can be a server device. The components of the electronic device can include, but are not limited to, at least one processor, at least one memory, a bus connecting different system components including the memory and the processor.

[0104] The bus includes a data bus, an address bus, and a control bus.

[0105] The memory can include volatile memory, such as random access memory (RAM) and / or cache memory, and can further include non-volatile memory, such as read-only memory (ROM).

[0106] The memory can also include program tools with a set of (at least one) program modules, such as each of or some combination of: an operating system, one or more application programs, other program modules, and program data, which can include implementation of a network environment.

[0107] The processor performs various function applications and data processing by running the computer program stored in the memory.

[0108] The electronic device can also communicate with one or more external devices (such as a keyboard, a pointing device, etc.) through an input / output (I / O) interface. And the electronic device can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter. The network adapter communicates with other modules of the electronic device through the bus. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (Redundant Array of Independent Disks) systems, tape drives, and data backup storage systems, etc.

[0109] It should be noted that although several units / modules or sub-units / modules of the electronic device are mentioned in the above detailed description, such division is merely exemplary and not mandatory. Indeed, according to an implementation of the present application, the features and functionalities of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functionalities of one unit / module described above can be further divided into units / modules embodied by several units / modules.

[0110] Embodiment 4

[0111] A computer readable storage medium, the readable storage medium storing a computer program, the program being executed by a processor to implement the steps of the reverse storage method of field permissions in embodiment 1.

[0112] More specifically, the readable storage medium can include, but is not limited to, a portable disc, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0113] In a possible implementation, the present disclosure can also be implemented in the form of a program product, which includes program code for causing the terminal device to perform the steps of the reverse storage method of field permissions described in embodiment 1 when the program product is run on the terminal device.

[0114] The program code for implementing the present disclosure can be written in any combination of one or more programming languages, and can be executed entirely on the user device, partially on the user device and partially on a remote device, or entirely on a remote device, as a stand-alone software package, or partially on the user device and partially on a remote device.

[0115] Although the embodiments of the present disclosure have been shown and described, it will be understood by those of ordinary skill in the art that various changes, modifications, alternatives, and variations can be made thereto without departing from the principles and spirit of the present disclosure, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for reverse storage of field authority, characterized in that, The method comprises the following steps: acquiring field permission data; acquiring dynamic table permission and view permission at the same time as acquiring the field permission data, and directly storing the dynamic table permission and the view permission without performing a NOT operation; filtering out authorized field permission data in the field permission data to retain unauthorized field permission data; performing a NOT operation on the unauthorized field permission data to obtain reverse storage field permission data; storing the reverse storage field permission data; before storing the reverse storage field permission data, further comprising the following steps: determining whether there is the reverse storage field permission data, and if there is the reverse storage field permission data, merging the dynamic table permission, the view permission and the reverse storage field permission data obtained at the same time as a final field permission set; and if there is no reverse storage field permission data, merging the dynamic table permission and the view permission as a final field permission set.

2. The method of claim 1, wherein the field authority is stored in reverse. before acquiring the field permission data, further comprising the following steps: defining a reverse storage structure of field permission, and the reverse storage structure comprises one or more of the following parameters: field ID, table ID, non-reading permission, non-writing permission, non-deleting permission.

3. The method of claim 2, wherein the field authority is stored in reverse. after acquiring the final field permission set, further comprising the following steps: acquiring a dynamic table and view field set to acquire all field sets that need to be output.

4. The method of claim 3, wherein the field authority is stored in reverse. after acquiring all field sets that need to be output, further comprising the following steps: performing permission identification on the dynamic table, the view field set and the final field permission set, and screening out an effective field set through intersection calculation.

5. The method of claim 4, wherein the field authority is stored in reverse. after screening out the effective field set, further comprising the step of outputting the effective field set.

6. A reverse storage system of field authority, using the reverse storage method of field authority as claimed in any one of claims 1 to 5, characterized by, comprise: a field permission acquisition module that acquires field permission data; an authorized field filtering module that filters out authorized field permission data in the field permission data to retain unauthorized field permission data; a NOT operation module that performs a NOT operation on the unauthorized field permission data to obtain reverse storage field permission data; a reverse storage module that stores the reverse storage field permission data.

7. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the steps of the reverse storage method of field permission according to any one of claims 1 to 5.

8. A computer-readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the reverse storage method of field permission according to any one of claims 1 to 5.

Images