CN111400696A - Data table authority processing method and device, computer equipment and storage medium - Google Patents

Abstract

The embodiments of the present application belong to the technical field of management, and relate to a method for processing data table rights, including: receiving a model file and a rights file; The user class has the permission to view the corresponding data table; use the model file to fetch data from the database to generate the data table, name the data table according to the preset rules, and generate the data table name; put the permission user class and the data table name in the database Associative storage; provide front-end pages, when receiving the data table name sent by the front-end page, determine the permission user class with viewing rights according to the data table name, and display it to the user. The present application also provides a data table permission processing device, computer equipment and storage medium. The present application realizes the management of the viewing authority of the data table, and the user can self-check to know the user class that has the authority to view the corresponding data table.

Description

Processing method, device, computer equipment and storage medium for data table rights

technical field

The present application relates to the field of big data technologies, and in particular, to a method, device, computer equipment and storage medium for processing data table permissions.

Background technique

The data table is stored in the system, and different user classes have different viewing permissions for the data table. According to the different permissions of the user class, the amount of information in the data table that the corresponding user can view is also different.

The user's permission to view the data table depends on the operator logging in to the production server to find the files handed over by the developer; however, because there are a large number of data tables in the system, each data table needs to be viewed by the operator one by one. , so it is very labor-intensive, resulting in low efficiency and high operating costs.

SUMMARY OF THE INVENTION

The purpose of the embodiments of the present application is to propose a method for processing data table permissions, so as to realize that the user can automatically know the user class that has the permission to view the corresponding data table through the front-end page.

In order to solve the above-mentioned technical problems, the embodiment of the present application provides a method for processing data table permissions, which adopts the following technical solutions:

A method for processing data table permissions, comprising the following steps:

Receive at least two different model files and at least two different permissions files that developers hand over to the production environment;

Parse the authority file, and perform weighting processing on the model file to obtain a model file with added authority control, wherein the authority file includes at least one authority user class, and the authority user class has the authority to view the corresponding data table ;

Use the model file with added authority control to call data from the database to generate a data table with added authority control, and name the data table according to preset rules to generate a data table name;

storing the privileged user class in association with the data table name in the database; and

Provide a front-end page, when receiving the data table name sent by the front-end page, determine the permission user class with viewing permission according to the data table name, and display the permission user class with the permission to view the corresponding data table to the user through the front-end page.

Further, the step of parsing the authority file and performing weighting processing on the model file includes:

Use a weighting tool to parse the permission file, and extract the permission user class, model name and weighting requirement in the permission file;

Determine the corresponding model file according to the extracted model name;

The permission limit is obtained according to the weighting requirement, and the permission limit and the permission user class are added to the model file to obtain a model file with permission control added.

Further, the described data table is named according to a preset rule, and the step of generating the data table name includes:

Identify the current year, month and data type in the data table, name the data table, and generate a data table name.

Further, the step of storing the permission user class and the data table name in association with the database includes:

After processing all the model files and permission files handed over by the current developer, store the generated data table name in association with the permission user class, and generate a lookup table;

Determine whether a lookup table is stored in the database;

If the lookup table is not stored in the database, the generated lookup table will be written into the database;

If a lookup table is stored in the database, the original lookup table is deleted, and the generated lookup table is written into the database.

Further, after the step of parsing the authority file and performing weighting processing on the model file to obtain a model file with authority control added, the method further includes:

Regularly check the data sheet is checked;

If the time difference between the last login time of the currently detected data table and the current detection time is greater than a preset time period, the currently detected data table is hidden.

Further, after the step of parsing the authority file and performing weighting processing on the model file to obtain a model file for adding authority control, the method further includes:

Associating the pre-stored first user ID with at least one privileged user class, so that the first user ID has the right to view the data table controlled by the privileged user class;

Periodically detect the login situation of the first user ID;

If the time difference between the last login time of the first user ID and the current detection time is greater than a preset time period, the association between the first user ID and the authorized user class is released.

Further, after the step of associating the pre-stored first user ID with at least one permission user class, so that the first user ID has the permission to view the data table controlled by the permission user class, further comprising: :

A front-end page is provided, when receiving a permission application request sent by the front-end page, the permission application request carries the permission user class and the second user ID, and the permission user class and the second user ID are sent to the administrator for review;

When receiving the consent instruction sent by the administrator, configure the permission user class for the second user ID, so that the second user ID has the permission to view the corresponding data table, and display it to the user through the front-end page Audit results.

In order to solve the above technical problem, the embodiment of the present application also provides a processing device for data table permissions, which adopts the following technical solutions:

A processing device for data table permissions, comprising:

a receiving module for receiving at least two different model files and at least two different permission files handed over to the production environment by the developer;

A weighting module, configured to parse the authority file and perform weighting processing on the model file to obtain a model file with added authority control, wherein the authority file includes at least one authority user class, and the authority user class has the ability to view Permissions corresponding to the data table;

A generation module is used for using the model file with added authority control to call data from the database to generate a data table with added authority control, and to name the data table according to preset rules, and to generate a data table name;

a storage module for storing the privileged user class and the name of the data table in the database in association; and

The providing module is used to provide the front-end page, when receiving the data table name sent by the front-end page, determine the permission user class with viewing authority according to the data table name, and show the user through the front-end page that has the authority to view the corresponding data table Permission user class.

In order to solve the above-mentioned technical problems, the embodiment of the present application also provides a computer device, which adopts the following technical solutions:

A computer device includes a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the processor implements the steps of the above method for processing data table permissions.

In order to solve the above technical problems, the embodiments of the present application also provide a computer-readable storage medium, which adopts the following technical solutions:

A computer-readable storage medium stores a computer program on the computer-readable storage medium, and when the computer program is executed by a processor, implements the steps of the above method for processing data table permissions.

Compared with the prior art, the embodiments of the present application mainly have the following beneficial effects:

The permissions corresponding to the user class and the data table are placed in the database, so that all users can self-check through the front-end page. Users only need to enter the name of the data table in the input box on the page, and click query to see which user classes have the ability to view the data. The permission of the table, the event personnel can quickly respond to the permission problem reported by the user, the operation personnel can quickly deal with the report permission error problem, and the developer can quickly view the report permission for the reference of report development; thereby helping enterprises to improve service quality and customer satisfaction When the user has not logged in for a long time, the association between the user ID and the authorized user class will be cancelled to ensure the information security in the system in time.

Description of drawings

In order to illustrate the solutions in the present application more clearly, the following will briefly introduce the accompanying drawings used in the description of the embodiments of the present application. For those of ordinary skill, other drawings can also be obtained from these drawings without any creative effort.

FIG. 1 is an exemplary system architecture diagram to which the present application can be applied;

2 is a flowchart of an embodiment of a method for processing data table permissions according to the present application;

Fig. 3 is the concrete flow chart of step S2 in Fig. 2;

Fig. 4 is the concrete flow chart of step S4 in Fig. 2;

5 is a flowchart of another embodiment of a method for processing data table permissions according to the present application;

6 is a flowchart of another embodiment in a method for processing data table permissions according to the present application;

7 is a schematic structural diagram of an embodiment of an apparatus for processing data table permissions according to the present application;

FIG. 8 is a schematic structural diagram of an embodiment of a computer device according to the present application.

Reference numerals: 200, computer equipment; 201, memory; 202, processor; 203, network interface; 300, processing device for data table authority; 301, receiving module; 302, weighting module; 303, generating module; 304, storage module; 305. Provide a module.

Detailed ways

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the technical field of this application; the terms used herein in the specification of the application are for the purpose of describing specific embodiments only It is not intended to limit the application; the terms "comprising" and "having" and any variations thereof in the description and claims of this application and the above description of the drawings are intended to cover non-exclusive inclusion. The terms "first", "second" and the like in the description and claims of the present application or the above drawings are used to distinguish different objects, rather than to describe a specific order.

Reference herein to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor a separate or alternative embodiment that is mutually exclusive of other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

In order to make those skilled in the art better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings.

As shown in FIG. 1 , the system architecture 100 may include terminal devices 101 , 102 , and 103 , a network 104 and a server 105 . The network 104 is a medium used to provide a communication link between the terminal devices 101 , 102 , 103 and the server 105 . The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages and the like. Various communication client applications may be installed on the terminal devices 101 , 102 and 103 , such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, and the like.

The terminal devices 101, 102, and 103 may be various electronic devices that have a display screen and support web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, moving image Expert Compression Standard Audio Layer 3), MP4 (Moving PictureExperts Group Audio Layer IV, Moving Picture Experts Group Audio Layer 4) Players, Laptops and Desktops, etc.

The server 105 may be a server that provides various services, such as a background server that provides support for the pages displayed on the terminal devices 101 , 102 , and 103 .

It should be noted that the method for processing data table permissions provided by the embodiments of the present application is generally executed by a server/terminal device, and correspondingly, the processing apparatus for data table permissions is generally set in the server/terminal device.

It should be understood that the numbers of terminal devices, networks and servers in FIG. 1 are merely illustrative. There can be any number of terminal devices, networks and servers according to implementation needs.

Continuing to refer to FIG. 2 , there is shown a flowchart of an embodiment of a method for processing data table permissions according to the present application. The processing method of the data table permission includes the following steps:

S1: Receive at least two different model files and at least two different permissions files that developers hand over to the production environment.

In this embodiment, the suffix names of the model file and the authority file are different, the suffix name of the model file is mdl, the suffix name of the authority file is xml, and the model name of the model file and the authority name of the authority file are one-to-one. Correspondence. The model name of the current model file is intercepted, and the authority name corresponding to the model name is identified according to the model name, so as to determine the corresponding authority file. Model files are used to retrieve data from the database to generate data tables. For example, if the model name of the current model file is a.mdl, then find the corresponding permission file by finding the permission name a.xml. In addition, the data table can be a report; the model file retrieves data including the required information such as the financial status, operating results and cash flow of the enterprise in a certain period from the database, thereby generating a report. The permission file (xml) is used to add permission to the model file, so that the report generated by the model file can only be viewed by the user class with the corresponding permission.

In this embodiment, the electronic device (for example, the server/terminal device shown in FIG. 1 ) on which the data table permission processing method runs can receive the model file and the permission handed over by the developer through a wired connection or a wireless connection. document. It should be pointed out that the above wireless connection methods may include but are not limited to 3G/4G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other wireless connection methods currently known or developed in the future .

S2: Parse the permission file, and perform weighting processing on the model file to obtain a model file with permission control added, wherein the permission file includes at least one permission user class, and the permission user class has the ability to view a corresponding data table permission.

In this embodiment, model files are weighted in the production environment, and permission control is added to the model files, so that only user classes with corresponding permissions can view the data tables generated by the corresponding model files. Of course, the present application may also parse the authority file after the model file generates the data table, and perform weighting processing on the data table. The model file is used to retrieve data from the database to generate a data table, and the permission file is used to add permissions to the model file, so that the data table generated by the model file can only be viewed by user classes with corresponding permissions.

Specifically, as shown in FIG. 3 , FIG. 3 is a specific flowchart of step S2 in FIG. 2 . In step S2, the steps of parsing the authority file and performing weighting processing on the model file include:

S21: Use a weighting tool to parse the authority file, and extract the authority user class, model name and weighting requirement in the authority file;

S22: Determine the corresponding model file according to the extracted model name;

S23: Obtain the permission limit according to the weighting requirement, and append the permission limit and the permission user class to the model file to obtain a model file to which permission control is added.

In this embodiment, a weighting tool is used to add the content in the authority file (xml) to the model (mdl) file, so that a layer of authority control is added to the model file. When the model file extracts data from the database, a data table is formed After that, only the permission user class with the corresponding permission can lift the permission restriction, and then view the corresponding data table; and when the weighting tool is not used to append the content in the permission file to the model file, the model file extracts data from the database to form The data table is viewable by all user classes without permission.

Of course, it is also possible to extract information such as the permission user class, model name, and weighting requirements in the permission file, and establish a corresponding relationship in the database for storage. Therefore, it is not necessary to perform weighting processing on the model file immediately. When the model file needs to be weighted, the permission user class stored in the database can be directly attached to the corresponding model file, without the need to re-receive and parse the permission file, which improves the response speed of the computer.

S3: Use the model file with added authority control to retrieve data from the database to generate a data table with added authority control, and name the data table according to a preset rule to generate a data table name.

In this embodiment, the name of the produced data table has a corresponding relationship with the data table to which the permission control is added. The data table to which permission control is added has a corresponding relationship with the model file to which permission control is added. The model file to which permission control is added has a corresponding relationship with the permission user class attached to it. Therefore, the data table name has a corresponding relationship with the permission user class. The name of the data table is generated according to the preset rules, which is convenient for the management of the data table.

Specifically, in step S3, that is, the data table is named according to a preset rule, and the step of generating the data table name includes:

Identify the current year, month and data type in the data table, name the data table, and generate a data table name.

In this embodiment, if the data type in the data table is a data type, it is a financial table, and if the data type in the data table is a statistical graph type, it is a statistical table. The year, month and data type in which the data table is generated only need to be obtained according to the name of the data table, which facilitates the unified management and identification of the data table by the relevant personnel.

S4: Associate and store the permission user class and the data table name in the database.

In this embodiment, the permission user class and the name of the data table are stored in association with each other in the database, so that the corresponding records are stored in the database, which facilitates calling and viewing of the corresponding association relationship.

Specifically, as shown in FIG. 4 , FIG. 4 is a specific flowchart of step S4 in FIG. 2 . In step S4, the step of storing the privileged user class and the name of the data table in association with the database includes:

S41: After processing all the model files and authority files handed over by the current developer, store the generated data table name in association with the authority user class, and generate a lookup table;

S42: Determine whether a lookup table is stored in the database;

S43: If the lookup table is not stored in the database, write the generated lookup table into the database;

S44: If the lookup table is stored in the database, delete the original lookup table, and write the generated lookup table into the database.

In this embodiment, before writing the lookup table into the database, confirm whether the lookup table has been stored in the database. If there is a lookup table stored in the database, it is an old lookup table, and the old lookup table is deleted; lookup table. If no lookup table is stored in the data, it means that the lookup table has not been written into the database before, and a new lookup table can be directly written. The old and new lookup tables are generated after processing all the model files and permission files at the current time and last time respectively; as time changes, the data in the original database changes, and the new model files are also different. There are also new changes in the permission user class of the model file. At this time, it is extremely complicated to modify everywhere, and the new model file and permission file can be retransmitted. Then the content of the new lookup table generated is different from the old lookup table. Then delete the old lookup table to avoid system identification errors, release the storage space of the system, and improve the response speed of the system.

Further, in the lookup table, the data table name and the permission user class have a one-to-one correspondence, a one-to-many relationship, a many-to-one relationship, or a many-to-many relationship.

In this embodiment, in the authority file, the data table name and the authority user class have a one-to-one, one-to-many or many-to-one relationship, which can be flexibly adjusted according to requirements.

S5: Provide a front-end page, when receiving the data table name sent by the front-end page, determine the permission user class with viewing permission according to the data table name, and display the permission user with the permission to view the corresponding data table to the user through the front-end page kind.

In this embodiment, the user can input the name of the data table to be queried through the front-end page, and according to the name of the data table input by the user, by looking up the corresponding relationship between the name of the data table and the permission user class in the database, it is determined that the user has the permission to view the data table The permission user class is displayed to the user through the front-end page, so that the user can know which user class has the permission to view the data table.

When incident personnel receive feedback on permission issues, they can quickly determine and respond to permission issues by querying on the front-end page; operators can also quickly deal with data table permission errors; developers can quickly view and confirm data table permissions through the front-end page , a reference for data sheet development. At the same time, it also realizes the monitoring of which data tables can be viewed by which users; for example: some important data tables cannot be viewed by everyone, but if the developer forgets to add permissions or forget to hand over the permission files, according to the front-end page By querying the information in the database, you can quickly monitor the privileged user class corresponding to the data table.

In practical applications, such as the application of reports: the data in the report is confidential and cannot allow everyone to view all the data. Through the front-end page, users can know which user classes have the permission to view the queried report, so that they can timely statistics and determine relevant permission information.

At the same time, the application can also provide a front-end page, when receiving the request for permission to apply sent by the front-end page, the request for permission to apply carries the permission user class and the second user ID, and the permission user class and the second user The ID is sent to the manager for review; when the consent instruction sent by the manager is received, the permission user class is configured for the second user ID, so that the second user ID has the permission to view the corresponding data table, And display the audit results to users through the front-end page.

In this embodiment, the user corresponding to the second user ID is an ordinary employee of the company. When the ordinary employee requests the permission to view the data table due to work needs, it is necessary to send an application carrying the corresponding second user ID through the front-end page. Permission request, and then through the review of the administrator, can obtain the permission to view the data table. The correspondence between the data tables and the authorized user classes in this application is preset by the people in the business department, that is, the people in the business department have pre-determined which data table can be viewed for which user classes; when the user needs to view a certain When a data table is used, it is necessary to first query which user classes have the permission to view the data table; and then apply for these permission user classes with permissions. After the administrator agrees, the user can obtain the permission user class, and then obtain the view. permissions for this data sheet. It is conducive to the clear management and control of the viewing authority of the data table, and ensures the information security of the data table.

In some optional implementations of this embodiment, as shown in FIG. 5 , FIG. 5 is a flowchart of another embodiment of a method for processing data table permissions according to the present application. After step S2, that is, after parsing the authority file and performing a weighting process on the model file to obtain a model file to which authority control is added, the electronic device may also perform the following steps:

S6: Regularly check the status of the data sheet being viewed;

S7 : If the time difference between the last login time of the currently detected data table and the current detection time is greater than a preset time period, the currently detected data table is hidden.

In this embodiment, if it is detected that a data table has not been viewed for a long time, the data table is hidden, so that even a user class with the authority to view the corresponding data table cannot view the data table; if the data table is hidden, the system is searching for the data table. The data table can be ignored when the data table is used to reduce the number of data tables searched by the system and improve the response speed of the system. When the data table is hidden for more than the preset time, send the data table name and start hiding time to the relevant personnel, and the relevant personnel will delete or unhide the data table according to the actual situation.

As shown in FIG. 6 , FIG. 6 is a flowchart of another embodiment of a method for processing data table permissions according to the present application. After step S2, that is, after parsing the authority file and performing a weighting process on the model file to obtain a model file for adding authority control, the method further includes:

S8: associate the pre-stored first user ID with at least one privileged user class, so that the first user ID has the right to view the data table controlled by the privileged user class;

S9: Regularly detect the login status of the first user ID;

S10: If the time difference between the last login time of the first user ID and the current detection time is greater than a preset time period, disassociate the first user ID with the authorized user class.

In this embodiment, the user corresponding to the first user ID is the supervisor, general manager, deputy general manager, etc. of each department of the company. According to the user's position authority, the corresponding first user ID is associated with different permission user classes. If the time difference between the last login time of the first user ID and the current detection time is greater than half a year, the authority will be withdrawn, and the association between the first user ID and the authority user class will be cancelled; the first user ID has not logged in for more than half a year, indicating that If the corresponding user of the first user ID resigns or takes a long vacation, the viewing authority of the first user ID that has not logged in for a long time is cancelled to ensure the security of information;

Of course, it is also possible to associate a pre-stored first user ID with at least one permission user class, so that the first user ID has the permission to view the data table controlled by the permission user class, and regularly detect the first user ID to view the In the case of each data table, determine the data table that has not been viewed by the first user ID for more than a preset time period, identify the authorized user class corresponding to the data table, disassociate the authorized user class with the first user ID, and retain other The association relationship between the authorized user class and the first user ID. In this solution, no matter how many data tables the permission user class has viewing permission, as long as any data table under the permission user class has not been viewed by the first user ID for more than a preset time, the permission user class and the first user ID will be released. The association of a user ID makes it impossible for the first user ID to view all the data tables under the privileged user class; the security of all the data tables under the user class is protected.

In addition, it is also possible to associate a pre-stored first user ID with at least one permission user class, so that the first user ID has the permission to view the data table controlled by the permission user class, and regularly detect the first user ID checks the situation of each data table, determines the data table that has not been viewed by the first user ID for more than a preset time period, and identifies the authorized user class corresponding to the data table, if all data tables under the authorized user class exceed the predetermined time period If the set time is not checked by the first user ID, the association between the authorized user class and the first user ID is released, and the association between other authorized user classes and the first user ID is retained. In this solution, all data tables under the permission user class are required to be unchecked by the first user ID for more than a preset time, so that the association between the permission user class and the first user ID is released, so as to prevent erroneous release and prevent impact. The user's work progress.

The above-mentioned implementation manner of the present application can be flexibly selected according to the actual situation.

Those of ordinary skill in the art can understand that the realization of all or part of the processes in the methods of the above embodiments can be accomplished by instructing relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the program is During execution, it may include the processes of the embodiments of the above-mentioned methods. The aforementioned storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM).

It should be understood that although the various steps in the flowchart of the accompanying drawings are sequentially shown in the order indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order and may be performed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and the execution sequence is also It does not have to be performed sequentially, but may be performed alternately or alternately with other steps or at least a portion of sub-steps or stages of other steps.

With further reference to FIG. 7 , as an implementation of the method shown in FIG. 2 above, the present application provides an embodiment of a data table permission processing apparatus. The apparatus embodiment corresponds to the method embodiment shown in FIG. 2 . The device can be specifically applied to various electronic devices.

As shown in FIG. 7 , the apparatus 300 for processing data table permissions according to this embodiment includes: a receiving module 301 , a weighting module 302 , a generating module 303 , a storage module 304 and a providing module 305 . in:

A receiving module 301, configured to receive at least two different model files and at least two different permission files that are handed over to the production environment by the developer;

The weighting module 302 is configured to parse the authority file and perform weighting processing on the model file to obtain a model file with added authority control, wherein the authority file includes at least one authority user class, and the authority user class has Permission to view the corresponding data sheet;

The generating module 303 is configured to use the model file for adding authority control to call data from the database to generate a data table for adding authority control, and to name the data table according to a preset rule to generate a data table name;

a storage module 304, configured to associate and store the privileged user class and the data table name in the database; and

The providing module 305 is configured to provide a front-end page, when receiving the data table name sent by the front-end page, determine a permission user class with viewing authority according to the data table name, and display the corresponding data table to the user through the front-end page The permission user class for the permission.

The weighting module 302 includes a parsing unit, an extraction unit and an additional unit. The parsing unit is configured to use a weighting tool to parse the authority file, and extract the authority user class, model name and weighting requirement in the authority file; the extraction unit is configured to determine the corresponding model according to the extracted model name file; the appending unit is configured to obtain the permission limit according to the weighting requirement, and append the permission limit and the permission user class to the model file to obtain the model file to which permission control is added.

The storage module 304 includes a creation unit, a judgment unit, a writing unit and a deletion unit. The creation unit is used to process all the model files and authority files handed over by the current developer, store the generated data table name in association with the authority user class, and generate a lookup table; the judgment unit is used to judge whether the data in the database is A look-up table is stored; the writing unit is used to write the generated look-up table into the database when the look-up table is not stored in the database; the deletion unit is used to delete the original look-up table when the look-up table is stored in the database table, and the generated lookup table is written into the database through the writing unit.

The processing device 300 of the data table authority also includes a detection module and a hidden module, the detection module is used to regularly detect the situation of the data table being viewed; the hidden module is used for when the current detected data table was last logged in time and When the time difference between the current detection time is greater than a preset time period, the currently detected data table is hidden.

In this embodiment, compared to only relying on the operator to log in to the production server to find the development and handover files, it is possible to determine which user classes have the authority to view the corresponding data tables, and there are hundreds of thousands of data tables in each system. Each data table is viewed one by one by the operator, which is very labor-intensive, the operating cost remains high, and customer satisfaction is also affected. In the database, all users can self-check through the front-end page. Users only need to enter the name of the data table in the input box on the page, and click query to see which user classes have the permission to view the data table. Event personnel can quickly respond to user reports. The operator can quickly deal with the report permission problem, and the developer can quickly view the report permission for the reference of report development; thus helping the enterprise to improve the service quality and customer satisfaction; when the user has not logged in for a long time, the user The association between the ID and the authorized user class is canceled, and the information security in the system is ensured in a timely manner.

To solve the above technical problems, the embodiments of the present application also provide computer equipment. For details, please refer to FIG. 8 , which is a block diagram of a basic structure of a computer device according to this embodiment.

The computer device 200 includes a memory 201 , a processor 202 , and a network interface 203 that communicate with each other through a system bus. It should be noted that only the computer device 200 with components 201-203 is shown in the figure, but it should be understood that implementation of all shown components is not required, and more or less components may be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculation and/or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, special-purpose Integrated circuit (Application Specific Integrated Circuit, ASIC), Programmable Gate Array (Field-Programmable Gate Array, FPGA), Digital Signal Processor (Digital Signal Processor, DSP), embedded devices, etc.

The computer equipment may be a desktop computer, a notebook computer, a palmtop computer, a cloud server and other computing equipment. The computer device can perform human-computer interaction with the user through a keyboard, a mouse, a remote control, a touch pad or a voice control device.

The memory 201 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static Random Access Memory (SRAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Programmable Read Only Memory (PROM), Magnetic Memory, Magnetic Disk, Optical Disk, etc. In some embodiments, the memory 201 may be an internal storage unit of the computer device 200 , such as a hard disk or a memory of the computer device 200 . In other embodiments, the memory 201 may also be an external storage device of the computer device 200 , for example, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital disk equipped on the computer device 200 (Secure Digital, SD) card, flash memory card (Flash Card) and so on. Of course, the memory 201 may also include both an internal storage unit of the computer device 200 and an external storage device thereof. In this embodiment, the memory 201 is generally used to store the operating system and various application software installed in the computer device 200, such as program codes of a method for processing data table permissions. In addition, the memory 201 can also be used to temporarily store various types of data that have been output or will be output.

In some embodiments, the processor 202 may be a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 202 is typically used to control the overall operation of the computer device 200 . In this embodiment, the processor 202 is configured to run the program code or process data stored in the memory 201 , for example, the program code of a method for processing data table permissions.

The network interface 203 may include a wireless network interface or a wired network interface, and the network interface 203 is generally used to establish a communication connection between the computer device 200 and other electronic devices.

In this embodiment, the user class with the right to view the corresponding data table can be displayed to the user directly through the computer device, which facilitates management and improves user experience.

The present application also provides another implementation manner, which is to provide a computer-readable storage medium, where the computer-readable storage medium stores a processing program for data table rights, and the processing program for data table rights can be processed by at least one The processor executes, so that the at least one processor executes the steps of the method for processing the permissions of the data table as described above.

In this embodiment, the data table permission processing program stored in the computer-readable storage medium can effectively manage the data table viewing authority, and realize the user's self-service query of the data table permission user class.

From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of this application.

Obviously, the above-described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The accompanying drawings show the preferred embodiments of the present application, but do not limit the scope of the patent of the present application. This application may be embodied in many different forms, rather these embodiments are provided so that a thorough and complete understanding of the disclosure of this application is provided. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or perform equivalent replacements for some of the technical features. . Any equivalent structure made by using the contents of the description and drawings of the present application, which is directly or indirectly used in other related technical fields, is also within the scope of protection of the patent of the present application.

Claims (10)

1. A method for processing data table permissions, comprising the steps of:

receiving at least two different model files and at least two different rights files that a developer hands over to a production environment;

analyzing the authority file, and carrying out weighting processing on the model file to obtain a model file added with authority control, wherein the authority file comprises at least one authority user class which has authority for viewing a corresponding data table;

calling data from a database by using the model file added with the authority control to generate a data table added with the authority control, naming the data table according to a preset rule, and generating a data table name;

storing the authority user class and the name of the data table in a database in an associated manner; and

providing a front-end page, determining an authority user class with viewing authority according to the data table name when the data table name sent by the front-end page is received, and displaying the authority user class with the authority for viewing the corresponding data table to a user through the front-end page.

2. The method of claim 1, wherein the step of parsing the rights file and weighting the model file comprises:

analyzing the authority file by using a weighting tool, and extracting an authority user class, a model name and a weighting requirement in the authority file;

determining a corresponding model file according to the extracted model name;

and acquiring authority limit according to the weighting requirement, and attaching the authority limit and the authority user class to the model file to acquire the model file added with the authority control.

3. The method for processing data table permission according to claim 2, wherein the step of naming the data table according to a preset rule and generating a data table name comprises:

and identifying the current year, month and data type in the data table, naming the data table, and generating a data table name.

4. The method for processing the authority of the data table according to any one of claims 1 to 3, wherein the step of storing the authority user class and the name of the data table in association with each other in a database comprises:

after all the model files and the authority files handed over by the current developer are processed, the generated data table name and the authority user class are stored in an associated mode to generate a lookup table;

judging whether a lookup table is stored in a database or not;

if the database does not store the lookup table, writing the generated lookup table into the database;

if the database stores the lookup table, deleting the original lookup table and writing the generated lookup table into the database.

5. The method for processing the authority of the data table according to any one of claims 1 to 3, further comprising, after the step of parsing the authority file and performing weighting processing on the model file to obtain the model file added with the authority control:

regularly detecting the viewing condition of the data table;

and if the time difference value between the last login time of the currently detected data table and the current detection time is greater than a preset time period, hiding the currently detected data table.

6. The method for processing authority of data table according to any of claims 1 to 3, further comprising, after the step of parsing the authority file and performing weighting processing on the model file to obtain a model file added with authority control:

associating a pre-stored first user ID with at least one authority user class so that the first user ID has authority for viewing a data table controlled by the authority user class;

regularly detecting the login condition of the first user ID;

and if the time difference between the last login time of the first user ID and the current detection time is greater than a preset time period, releasing the association between the first user ID and the authorized user class.

7. The method for processing data table permission according to claim 6, after the step of associating a pre-stored first user ID with at least one permission user class so that the first user ID has permission to view the data table controlled by the permission user class, further comprising:

providing a front-end page, when receiving an application authority request sent by the front-end page, carrying an authority user class and a second user ID by the application authority request, and sending the authority user class and the second user ID to a manager for auditing;

and when an agreement instruction sent by a manager is received, configuring the authority user class for the second user ID so that the second user ID has the authority of viewing the corresponding data table, and displaying an auditing result to a user through a front-end page.

8. An apparatus for processing data table permissions, comprising:

the system comprises a receiving module, a generating module and a processing module, wherein the receiving module is used for receiving at least two different model files and at least two different authority files which are handed over to a production environment by a developer;

the weighting module is used for analyzing the authority file and carrying out weighting processing on the model file to obtain a model file added with authority control, wherein the authority file comprises at least one authority user class which has authority for viewing a corresponding data table;

the generating module is used for calling data from a database by using the model file added with the authority control to generate a data table added with the authority control, naming the data table according to a preset rule and generating a data table name;

the storage module is used for storing the authority user class and the name of the data table in a database in a correlation manner; and

and the providing module is used for providing a front-end page, determining the authority user class with the viewing authority according to the data table name when the data table name sent by the front-end page is received, and displaying the authority user class with the viewing authority corresponding to the data table to the user through the front-end page.

9. A computer arrangement, characterized by a memory in which a computer program is stored and a processor which, when executing the computer program, carries out the steps of a method of processing data table permissions according to any of claims 1 to 7.

10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method of processing data table permissions according to any of claims 1 to 7.

Images