CN111597165A - Database management method, terminal and storage medium - Google Patents
Database management method, terminal and storage medium Download PDFInfo
- Publication number
- CN111597165A CN111597165A CN202010304148.XA CN202010304148A CN111597165A CN 111597165 A CN111597165 A CN 111597165A CN 202010304148 A CN202010304148 A CN 202010304148A CN 111597165 A CN111597165 A CN 111597165A
- Authority
- CN
- China
- Prior art keywords
- database
- user
- information
- updating
- current version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a database management method, a terminal and a storage medium, wherein the database management method comprises the following steps: acquiring input user information, and entering a corresponding management interface according to the user information and an interface option selected by a user; recording the updating operation of the user in the management interface and the updating information of the user to the database; checking the current version of the database according to the updating operation and the updating information; and updating the current version of the database according to the checking result, or restoring the current version of the database to the previous version. When the user updates the database, the updating operation executed by the user and the corresponding updating information are recorded, so that the version of the database is verified according to the recorded information, and the version of the database is updated or recovered by managing data change in the database.
Description
Technical Field
The present invention relates to the field of terminal applications, and in particular, to a database management method, a terminal, and a storage medium.
Background
In the software development process, the version of the database needs to be managed and controlled, when a plurality of persons develop a database management and application system at the same time, the reasonable method is adopted to monitor the change of objects such as a data table, a storage process, a view and the like in the database, and the method is a very important link in the database management process.
Because, each time the database is changed, detailed records are required to be made; therefore, in the process of development, processes such as adding columns in a data table, modifying columns and modifying stored processes/views are often involved; after the data in the database changes, the previously defined database objects are lost, so a complete database version management method is required to manage the database.
Accordingly, the prior art is yet to be improved and developed.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a database management method, a terminal and a storage medium, which manage data changes in a database through a database management tool, so as to facilitate developers to update or recover the version of the database.
The technical scheme adopted by the invention for solving the technical problem is as follows:
in a first aspect, the present invention provides a database management method, wherein the database management method includes the following steps:
acquiring input user information, and entering a corresponding management interface according to the user information and an interface option selected by a user;
recording the updating operation of the user in the management interface and the updating information of the user to the database;
checking the current version of the database according to the updating operation and the updating information;
and updating the current version of the database according to the checking result, or restoring the current version of the database to the previous version.
Further, still include:
and setting user authority in advance according to the user information.
Further, the acquiring the input user information and entering the corresponding management interface according to the user information and the interface options selected by the user specifically includes the following steps:
acquiring user information input by the user;
verifying the user information and determining the user authority of the user;
and acquiring the interface options selected by the user, and entering a corresponding management interface according to the interface options and the user permission.
Further, the recording the update operation of the user in the management interface and the update information of the user to the database specifically includes the following steps:
screening users entering the management interface according to preset conditions;
recording the updating operation, the updating information, the updated content and the updating time executed by the selected user;
and generating an update log according to the update operation, the update information, the updated content and the update time.
Further, the verifying the current version of the database according to the update operation and the update information specifically includes the following steps:
checking the current version of the database according to the update log, and judging whether a definition object of the database in the current version is updated or not;
if the definition object of the database in the current version is not updated, judging that the current version of the database is not abnormal;
and if the definition object of the database in the current version is updated, judging that the current version of the database is abnormal.
Further, the updating the current version of the database according to the verification result specifically includes the following steps:
searching a position corresponding to the updated content according to the update log;
setting a corresponding updating node at the searched position;
and writing the updating information in the updating log into the updating node so as to update the current version of the database.
Further, the restoring the current version of the database to the previous version specifically includes the following steps:
searching an original definition object of the database according to the updated content;
and restoring the current version of the database to the previous version according to the original definition object.
Further, the management interface includes: a user management interface, a role management interface, and a node management interface.
In a second aspect, the present invention further provides a terminal, which includes a processor, and a memory connected to the processor, where the memory stores a database management program, and the database management program, when executed by the processor, is used to implement the operations of the database management method according to the first aspect.
In a third aspect, the present invention further provides a storage medium, wherein the storage medium stores a database management program, and the database management program is used for implementing the operations of the database management method according to the first aspect when executed by a processor.
The invention adopts the technical scheme and has the following effects:
when the user updates the database, the updating operation executed by the user and the corresponding updating information are recorded, so that the version of the database is verified according to the recorded information, and the version of the database is updated or recovered by managing data change in the database.
Drawings
FIG. 1 is a flow chart of a database management method in an embodiment of the invention.
FIG. 2 is a flow chart illustrating the processing of the user management interface in an embodiment of the present invention.
FIG. 3 is a flow chart illustrating the processing of a role management interface in an embodiment of the present invention.
FIG. 4 is a flowchart illustrating processing of a node management interface according to an embodiment of the present invention.
Fig. 5 is a functional schematic diagram of a terminal in an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer and clearer, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Example one
In the process of software development, no matter developers or database operation maintenance personnel, common scripts needing to be stored exist, the existing storage mode is to store the scripts in a file form through SQL format codes, and the storage mode is not convenient for general users to use and is also convenient for managers to classify and manage.
In order to facilitate the management of the database by the software development team, the present embodiment provides a database management method, which is applied to a terminal, where the terminal includes but is not limited to: mobile terminals, tablets, computers and the like; the terminal is provided with a management tool for managing the database version, and a software developer team can utilize the management tool to manage the version of the database, so that the application program and the database are arranged in the same version, and developers can trace the problems in the published program conveniently in the development process.
As shown in fig. 1, in an implementation manner of this embodiment, the database management method includes the following steps:
and S100, acquiring input user information, and entering a corresponding management interface according to the user information and the interface options selected by the user.
In the process of software development, a database version is automatically covered in the storage process of the database version, so that the definition of an object of the previous database version is lost; for example, developer a creates a storage process "ProcA" and developer B modifies the storage process "ProcA", which will be overwritten by the modifications made by developer B, resulting in the loss and inability to recover of the previously defined storage process.
By the management tool of the embodiment, all operations of a certain database can be completely recorded; by searching the operation record, the database operation executed by the operator can be obtained; for example, it may be found that the stored procedure "ProcA" was created by developer a and modified at some point in time by developer B.
During the software development process, the upgrading of the application program or the modification of the database may cause the database to have problems, such as the error report of the database or the performance reduction of the database, so that the management of the database version is very important; the management tool adopted in the embodiment can quickly check the difference between the current database version and the previous database version, and inquire the abnormity of the database according to specific conditions, thereby eliminating the abnormity and keeping the database running stably.
Specifically, before using the management tool, user permissions of users (i.e., software developers) need to be set, and user information may be input in the management tool when the user permissions of the users are set, where the user information includes information such as a user name, a user password, and a user position; then, the user authority for using the management tool is set according to the user information input by the user, so that an administrator can set the operation authority of each user according to the user authority.
By setting the user permission, corresponding permissions can be distributed for different users, so that each user can perform its own job, and misoperation is avoided; for example: the deletion error occurs because the meaning of the data packet in the database is unknown to individual users.
Namely, before the step S100, the method further includes the following steps:
and S001, setting user authority in advance according to the user information.
In this embodiment, after setting the user authority, each user may use a function in the corresponding management interface according to the user authority of the user, and perform a corresponding operation by the user authority; for example, modifying database version storage paths, finding database version exception information, and managing database versions, etc.
Specifically, when the user logs in the management tool, the user information input by the user may be acquired and verified, for example: verifying the user name, the user password, the user position and the like; if the user information is successfully verified, further determining the user authority of the user according to the user information; the user authority of each preset user is searched to obtain a search result, and the user authority of the current login management tool is determined according to the search result; and if the verification fails, carrying out corresponding prompt on a login interface of the management tool.
After the user information is verified and the user authority is determined, interface options selected by the user in a login interface can be obtained, and a corresponding management interface is entered according to the user authority and the interface options, wherein the management interface comprises: a user management interface, a role management interface and a node management interface; when the user enters the corresponding management interface, corresponding operations can be executed in the corresponding management interface to implement corresponding functions, for example: modifying data in the database, managing user information, managing database versions, and the like.
In the management tool, the user management interface may be configured to filter user information and edit the user information, where editing the user information includes: adding, modifying and deleting user information; the role management interface can be used for setting roles (namely user positions) of each user, and setting corresponding user permissions and the like according to the roles of the users; the node management interface can be used for inquiring information such as version information, patch information and modification information of the database, setting corresponding update nodes, and updating or recovering the version of the database according to the version verification result of the database.
Namely, the step S100 specifically includes the following steps:
step S110, obtaining user information input by the user;
step S120, verifying the user information and determining the user authority of the user;
step S130, obtaining the interface option selected by the user, and entering a corresponding management interface according to the interface option and the user authority.
In the embodiment, the user authority of each user is set, the input user information is verified when the user logs in the management tool, so that the user authority of the user is determined according to the input user information, and the user is given corresponding functions and operation authorities according to the determined user authority.
As shown in fig. 1, in an implementation manner of this embodiment, the database management method further includes the following steps:
and step S200, recording the updating operation of the user in the management interface and the updating information of the user to the database.
In this embodiment, after entering a corresponding management interface, each user may record operation information executed by the user through the management tool, and when updating data information in the database, record update information set by each user, so as to determine whether the current version of the database can be updated according to the recorded update operation and update information, that is, verify the current version of the database according to the update information and the update operation; meanwhile, the updating operation and the updating information are recorded, so that the follow-up maintenance personnel can conveniently inquire the corresponding abnormal condition from the recorded information.
Specifically, when the update operation and the update information are recorded, a user entering the management interface is screened according to a preset condition, where the preset condition is that a set job requirement is met, for example: setting the position requirement as a manager; then, selecting users meeting the job requirements, and recording the updating operation of the users; if a user clicks a database editing button, recording the operation executed by the user when the user finishes editing, and recording the updating information generated in the editing process and the modified content in the editing process; thereby generating an update log according to the update operation, the update information, the update time and the modified content (the original information before update) executed by the user; for example, the generated update log is: modified version information, version information 1.13, original version information 1.12, modification time XX and executor Y.
Further, when the update operation and the update information are recorded, the database may be synchronized according to the update information, and after each synchronization, a database version number based on the update information is generated, where the database version number may include a plurality of modifications or patches, but in some special cases, an additional tag needs to be set; for example: and managing certain changes in the database, classifying versions in the database, and other updating operations, and setting an additional tag so as to inquire or acquire a corresponding updating operation according to the additional tag.
That is, the step S200 specifically includes the following steps:
step S210, screening the users entering the management interface according to preset conditions;
step S220, recording the updating operation, the updating information, the updated content and the updating time executed by the selected user;
step 230, generating an update log according to the update operation, the update information, the updated content and the update time.
In the embodiment, the current version of the database can be verified according to the recorded information by recording the updating operation and the updating information of the user in the management interface, so that the database version can be recovered according to the recorded updating operation and the recorded updating information when the updating of the database version fails; moreover, the operation information and the updating information executed by each user are recorded, so that the follow-up maintenance personnel can conveniently inquire the corresponding abnormal condition from the recorded information.
As shown in fig. 1, in an implementation manner of this embodiment, the database management method further includes the following steps:
and step S300, checking the current version of the database according to the updating operation and the updating information.
In this embodiment, after the update operation and the update information are recorded, if it is detected that the user updates the current version of the database, the current version of the database is checked according to the update operation and the update information, so as to determine whether the current version of the database can be updated.
Specifically, when the current version of the database is checked, the definition object of the database may be checked according to the content in the update log, and when the update log includes the definition object of the database, it indicates that the definition object of the database in the current version is different from the definition object of the previous version; in short, when checking, determining whether the definition object of the database in the current version is updated, if the definition object of the database in the current version is not updated, determining that the current version of the database is not abnormal, and at this time, performing an update operation on the current version of the database; and if the definition object of the database in the current version is updated, judging that the current version of the database is abnormal, and indicating that the current version of the database is not suitable for updating.
Namely, the step S300 specifically includes the following steps:
step S310, checking the current version of the database according to the update log, and judging whether the definition object of the database in the current version is updated;
step S320, if the definition object of the database in the current version is not updated, judging that the current version of the database is not abnormal;
step S330, if the definition object of the database in the current version is updated, it is determined that the current version of the database is abnormal.
In this embodiment, the current version of the database is checked, so as to determine whether a defined object in the current version of the database is lost, and if the check is successful, the current version of the database is updated, so as to ensure the stability of the updated database in operation; if the verification fails, the lost definition object can be recovered according to specific conditions, so that errors can be quickly eliminated and the continuous and stable operation of the database is ensured.
As shown in fig. 1, in an implementation manner of this embodiment, the database management method further includes the following steps:
and step S400, updating the current version of the database according to the checking result, or restoring the current version of the database to the previous version.
In this embodiment, after the current version of the database is verified, the current version of the database may be updated according to the verification result, so that a user in subsequent development may stably operate the updated new version; or, the current version of the database can be restored to the previous version according to the checking result so as to restore the lost definition object according to the specific situation, thereby quickly eliminating errors and ensuring the continuous and stable operation of the database.
Specifically, when the current version of the database is updated, the position corresponding to the updated content is searched according to the update log, and a corresponding update node is set at the searched position; and then writing the updating information in the updating log into the updating node so as to update the current version of the database.
That is, in the step S400, the current version of the database is updated according to the verification result, which specifically includes the following steps:
step S411, searching the position corresponding to the updated content according to the update log;
step S412, setting corresponding updating nodes at the searched positions;
step S413, writing the update information in the update log into the update node, so as to update the current version of the database.
Specifically, when the current version of the database is restored, the definition object of the database may be searched according to the updated content in the update log, and then the lost definition object is restored according to the specific situation, thereby quickly eliminating the error and ensuring the continuous and stable operation of the database.
That is, in the step S400, the restoring the current version of the database to the previous version specifically includes the following steps:
step S421, searching the original defined object of the database according to the updated content;
step S422, restoring the current version of the database to the previous version according to the original definition object.
In actual application, different update operations are performed for different management interfaces, and the user management interface, the role management interface, and the node management interface are described below.
As shown in fig. 2, the following steps are included in the user management interface:
step S11, entering a user management page;
step S12, screening user information according to the conditions;
step S13, displaying users who satisfy the condition;
step S14, the user clicks the edit button;
step S15, judging whether the user has editing authority; if yes, go to step S16; if not, go to step S17;
step S16, entering an editing page;
step S17, prompting no editing authority, and returning to step S13;
and step S18, finishing editing and storing in a database.
When entering the user management page, if the user needs to add new user information, entering the new page according to a new button clicked by the user, and storing the new user information in the database after the user inputs the user information.
As shown in fig. 3, the role management interface includes the following steps:
step S21, entering a role management interface;
step S22, displaying the existing role information;
step S23, selecting a user;
step S24, the user clicks the edit button;
step S25, entering an editing interface;
and step S26, finishing editing and storing in a database.
When entering the role management interface, if the user needs to add new role information, entering a new page according to a new button clicked by the user, and storing the new role information into the database after the user inputs the role information.
As shown in fig. 4, the following steps are included in the node management interface:
step S31, selecting a branch to which the database version belongs;
step S32, adding a new modification node;
step S33, selecting modification information and modifying the modification information;
step S34, adding a patch;
step S35, selecting patch information;
and step S36, adding database version information.
The patch is a program for repairing a system bug in the database version, belongs to a child node under the database version, and is used for repairing problems and small changes in the version;
modifying the modification information refers to one-time modification of the database version, and is atomic data of the database version management tool; after associating with a version under a branch, the current version of the database is in an associated state.
The embodiment can realize that a plurality of persons modify the storage process executed by the software development or modify the function codes in the software, and control the database version of the software development, namely, the application program and the database are arranged under the same version, so that the problems of the published program can be traced in the software development process, and the tracking personnel of the software development can conveniently modify the database; and the version of the software development is verified, and the database version generated in the software development process is verified, so that the database is updated according to the verification result, or the database is restored to a stable state.
Example two
As shown in fig. 5, the present embodiment provides a terminal, which includes a processor 10, and a memory 20 connected to the processor 10, where the memory 20 stores a database management program, and the database management program is used for implementing the operations of the database management method according to the first embodiment when executed by the processor 10; as described above.
EXAMPLE III
The present embodiment provides a storage medium, wherein the storage medium stores a database management program, and the database management program is used for implementing the operations of the database management method according to the first embodiment when executed by a processor; as described above.
In summary, when the user updates the database, the present invention records the update operation performed by the user and the corresponding update information, so as to verify the version of the database according to the recorded information, and manage the data change in the database, thereby facilitating the developer to update or restore the version of the database.
Of course, it will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by a computer program instructing relevant hardware (such as a processor, a controller, etc.), and the program may be stored in a computer readable storage medium, and when executed, the program may include the processes of the above method embodiments. The storage medium may be a memory, a magnetic disk, an optical disk, etc.
It is to be understood that the invention is not limited to the examples described above, but that modifications and variations may be effected thereto by those of ordinary skill in the art in light of the foregoing description, and that all such modifications and variations are intended to be within the scope of the invention as defined by the appended claims.
Claims (10)
1. A database management method, characterized in that the database management method comprises the steps of:
acquiring input user information, and entering a corresponding management interface according to the user information and an interface option selected by a user;
recording the updating operation of the user in the management interface and the updating information of the user to the database;
checking the current version of the database according to the updating operation and the updating information;
and updating the current version of the database according to the checking result, or restoring the current version of the database to the previous version.
2. The database management method according to claim 1, further comprising:
and setting user authority in advance according to the user information.
3. The database management method according to claim 2, wherein the step of obtaining the input user information and entering the corresponding management interface according to the user information and the interface options selected by the user comprises the following steps:
acquiring user information input by the user;
verifying the user information and determining the user authority of the user;
and acquiring the interface options selected by the user, and entering a corresponding management interface according to the interface options and the user permission.
4. The database management method according to claim 1, wherein the recording of the update operation of the user in the management interface and the update information of the user on the database specifically includes the following steps:
screening users entering the management interface according to preset conditions;
recording the updating operation, the updating information, the updated content and the updating time executed by the selected user;
and generating an update log according to the update operation, the update information, the updated content and the update time.
5. The method of claim 4, wherein the checking the current version of the database according to the update operation and the update information comprises the steps of:
checking the current version of the database according to the update log, and judging whether a definition object of the database in the current version is updated or not;
if the definition object of the database in the current version is not updated, judging that the current version of the database is not abnormal;
and if the definition object of the database in the current version is updated, judging that the current version of the database is abnormal.
6. The database management method according to claim 5, wherein the updating the current version of the database according to the verification result includes the following steps:
searching a position corresponding to the updated content according to the update log;
setting a corresponding updating node at the searched position;
and writing the updating information in the updating log into the updating node so as to update the current version of the database.
7. The method for managing database according to claim 5, wherein the restoring the current version of the database to the previous version comprises the following steps:
searching an original definition object of the database according to the updated content;
and restoring the current version of the database to the previous version according to the original definition object.
8. The database management method of claim 3, wherein the management interface comprises: a user management interface, a role management interface, and a node management interface.
9. A terminal comprising a processor, and a memory coupled to the processor, the memory storing a database management program that, when executed by the processor, is configured to perform the operations of the database management method of any of claims 1-8.
10. A storage medium storing a database management program which, when executed by a processor, is configured to perform the operations of the database management method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010304148.XA CN111597165B (en) | 2020-04-17 | 2020-04-17 | Database management method, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010304148.XA CN111597165B (en) | 2020-04-17 | 2020-04-17 | Database management method, terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111597165A true CN111597165A (en) | 2020-08-28 |
| CN111597165B CN111597165B (en) | 2023-06-02 |
Family
ID=72185185
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010304148.XA Active CN111597165B (en) | 2020-04-17 | 2020-04-17 | Database management method, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111597165B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5043871A (en) * | 1986-03-26 | 1991-08-27 | Hitachi, Ltd. | Method and apparatus for database update/recovery |
| CN110059096A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | Data version management method, apparatus, equipment and storage medium |
| CN110569311A (en) * | 2019-10-30 | 2019-12-13 | 上海商魁信息科技有限公司 | Data synchronization method and device for database and computer storage medium |
-
2020
- 2020-04-17 CN CN202010304148.XA patent/CN111597165B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5043871A (en) * | 1986-03-26 | 1991-08-27 | Hitachi, Ltd. | Method and apparatus for database update/recovery |
| CN110059096A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | Data version management method, apparatus, equipment and storage medium |
| CN110569311A (en) * | 2019-10-30 | 2019-12-13 | 上海商魁信息科技有限公司 | Data synchronization method and device for database and computer storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 余颖,董旭源,高宏: "C/S模式管理信息系统实现自动升级和维护的方法", 佳木斯大学学报(自然科学版) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111597165B (en) | 2023-06-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9710367B1 (en) | Method and system for dynamic test case creation and documentation to the test repository through automation | |
| US11620277B2 (en) | Transaction processing at non-relational databases | |
| US9519675B2 (en) | Data access management during zero downtime upgrade | |
| US8037452B2 (en) | Task aware source checkin and build | |
| CA3131079A1 (en) | Test case generation method and device, computer equipment and storage medium | |
| US20060288344A1 (en) | Method and apparatus for upgrading a software application in the presence of user modifications | |
| US9971595B1 (en) | Techniques for automated database deployment | |
| US10146628B2 (en) | Software backup and restoration procedures using application and file monitoring | |
| CN111324522A (en) | Automatic test system and method | |
| US11055078B2 (en) | Systems and methods for deploying software products to environments | |
| US10048978B2 (en) | Apparatus and method for identifying a virtual machine having changeable settings | |
| CN102193841B (en) | Backup method and device of Subversion configuration database | |
| US20230072825A1 (en) | Database Schema Branching Workflow, with Support for Data, Keyspaces and VSchemas | |
| CN112732300A (en) | Data packet updating method and device, electronic equipment and readable storage medium | |
| EP3416069A1 (en) | Propagated deletion of database records and derived data | |
| US20220043774A1 (en) | Systems, methods, and storage media for transferring data files | |
| CN116226092B (en) | Database updating method and device | |
| CN111597165B (en) | Database management method, terminal and storage medium | |
| US20080172659A1 (en) | Harmonizing a test file and test configuration in a revision control system | |
| US10204134B2 (en) | Automatic detection of problems in a large-scale multi-record update system and method | |
| CN110597781A (en) | Flashback deletion method and system for database | |
| CN110928945A (en) | Data processing method and device for database and data processing system | |
| US9946534B1 (en) | Techniques for automated database deployment | |
| US12032589B2 (en) | Bypassing database automations | |
| CN113778997B (en) | Database version management method, system and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |