Database object manager and management method

Abstract

The invention discloses a database object manager and a management method, the manager realizes operation on a database object through interface design, and the manager comprises a database object creating module for creating and modifying the database object, the database object comprises one or more of a library, a mode, a table, an index, a partition, a constraint, a view, a sequence value, a storage process, a function, a packet, a user and a role; the database object management module is used for checking and modifying a database object, operating data, editing SQL (Structured Query Language), checking a table structure, and importing and exporting the table structure and table data; and the database object maintenance module is used for realizing table statistical analysis, index reconstruction, view compilation and modification, trigger compilation and modification, storage process and function compilation of database objects. Through the interface operation, the user can better use the database.

Description

Technical Field

[0001] The present invention relates to the technical field of database management, and particularly to a database object manager and a management method. Background Art

[0002] A database is a warehouse for storing data. It has a large storage space and can store millions, tens of millions, or even hundreds of millions of pieces of data. However, the database does not store data randomly but follows certain rules, otherwise the query efficiency will be very low. The current world is an Internet world full of data, flooded with a large amount of data, that is, this Internet world is a data world, and the sources of data are numerous, such as travel records, consumption records, browsed web pages, sent messages, and so on.

[0003] However, with the advent of the big data era, the data warehouse has gradually transformed into a distributed architecture, and due to the intricate complexity of the business itself, when database administrators use database objects, many problems occur, such as a large variety and quantity of database objects, inconvenient operations, and so on. Summary of the Invention

[0004] The purpose of the present invention is to provide a database object manager and a management method to solve the technical problem of how to facilitate users to use the database.

[0005] The present invention is implemented by the following technical solutions: A database object manager realizes the operation of database objects through interface design, including a database object creation module, a database object management module, and a database object maintenance module. Among them, The database object creation module is used to realize the creation and modification of database objects, and the database objects include one or more of a library, a schema, a table, an index, a partition, a constraint, a view, a sequence value, a stored procedure, a function, a package, a user, and a role; The database object management module is used to realize the viewing, modification, data operation, SQL editing, table structure viewing, table structure and table data import and export of database objects; The database object maintenance module is used to realize the table statistical analysis, index reconstruction, view compilation, modification, trigger compilation, modification, stored procedure, and function compilation of database objects.

[0006] Furthermore, it further includes a database user permission display module. The database user permission display module intuitively displays the permissions owned by the user through the mapping of user permission codes, realizes the authorization of the user when creating a user, or modifies the permissions of the user in subsequent operations.

[0007] Further, it also includes an SQL editing and execution module. The SQL editing and execution module operates on database objects through an interface, specifically including: performing syntax parsing through an editor, parsing the executed SQL input by the user in the editing box, then sending the SQL to the database via JDBC, waiting for the database result to be returned, and displaying it in the result column.

[0008] Further, it also includes a backup and recovery module. The backup and recovery module performs backup and recovery through an interface, including at the library level, schema level, and table level.

[0009] Further, it also includes a scheduled job module. The scheduled job module sets scheduled jobs through an interface.

[0010] Further, it also includes an object DDL export module. The object DDL export module obtains information on specified database objects through getMetaData of JDBC and assembles the data into a complete executable DDL statement through parsing.

[0011] Further, it also includes a text data import and export module. The text data import and export module exports data by specifying a single table or multiple tables, and the export formats are txt, csv, and sql files.

[0012] Further, it also includes an SQL execution record module. The SQL execution record module is used to record operations on the interface for users to view.

[0013] A method for managing database objects, implemented based on the above-mentioned database object manager, includes the following steps: S1: Creating database objects; S2: Managing database objects; S3: Maintaining database objects.

[0014] The beneficial effects of the present invention are as follows: The present invention facilitates users to better use the database through interface operations. All operations on database objects can be executed through the interface, mainly realizing the creation and modification of database objects, the management of database objects, and the maintenance of database objects.

[0015] The present invention can also implement connection management for multiple databases and can realize the migration of table objects and data between homogeneous or heterogeneous databases. Description of the Drawings

[0016] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on the structures shown in these drawings.

[0017] Figure 1 It is the principle block diagram of the present invention; Figure 2 It is the flowchart for creating database objects; Figure 3 It is the flowchart for DDL export; Figure 4 It is the flowchart for text export. Detailed implementation manners

[0018] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. Generally, the components of the embodiments of the present invention described and illustrated in the drawings here can be arranged and designed in various different configurations.

[0019] It should be noted that: similar reference numerals and letters indicate similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0020] The following will describe in detail some implementation manners of the present invention with reference to the drawings. Without conflict, the following embodiments and the features in the embodiments can be combined with each other.

[0021] Refer to Figure 1 , a database object manager, which realizes the operation of database objects through interface design, including a database object creation module, a database object management module, and a database object maintenance module. Among them, the database object creation module is used to realize the creation and modification of database objects; the database object management module is used to realize the viewing, modification, data operation, SQL editing, table structure viewing, table structure and table data import and export of database objects; the database object maintenance module is used to realize the table statistical analysis, index reconstruction, view compilation, modification, trigger compilation, modification, stored procedure, and function compilation of database objects.

[0022] In this embodiment, the database objects include libraries, schemas, tables, indexes, partitions, constraints, views, sequence values, stored procedures, functions, packages, users, and roles, etc.

[0023] See Figure 2 , the creation of database objects includes: Schema name and schema owner remarks; Judge whether the schema name and schema owner content are not empty. If they are not empty, the creation is successful; if they are empty, a warning prompt box will pop up, and the schema name and schema owner will be remarked again.

[0024] In this embodiment, there is also a database user permission display module. The database user permission display module visually displays the permissions owned by the user through the mapping of user permission codes, realizes the authorization of users when creating users, or modifies the permissions of users in subsequent operations. This module mainly depends on the permission code mapping. The specific mapping can be: ACL_READ_ANY (0x1), / * Readable any * / ; ACL_UPDATE_ANY (0x2), / * Updatable, in any * / ; ACL_INSERT_ANY (0x4), / * Insertable, in any * / ; ACL_DELETE_ANY (0x8), / * Deletable, in any * / ; ACL_REF_ANY (0x10), / * Referable any * / ; ACL_EXECUTE_ANY (0x20), / * Executable any * / ; ACL_INDEX_ANY (0x40), / * Creatable any index * / ; ACL_CRE_ANY (0x100), / * Creatable any * / ; ACL_ALT_ANY (0x200), / * Modifiable any * / ; ACL_DROP_ANY (0x400), / * Deletable any * / ; ACL_BACKUP_ANY (0x800), / * Backupable any * / ; ACL_RESTORE_ANY (0x1000), / * Restorable any * / ; ACL_VACUUM_ANY (0x2000), / * Vacuumable any * / ; ACL_REPLICATION_ANY (0x4000), / * Synchronizable any * / ; ACL_REFRESH_ANY (0x8000), / * Refreshable any data * / ; ACL_GRANT_ANY (0x10000), / * Can grant any * / ; ACL_ENCRYPT_ANY (0x20000), / * Can encrypt any * / ; ACL_CRE_JOB (0x40000), / * Can create any scheduled job * / ; ACL_TRACE (0x80000), / * Can debug any connection * / ; ACL_AUDITOR (0x10000000), / * AUDITOR * / ; ACL_AUDIT_ADMIN (0x30000000), / * Audit management right * / ; ACL_SSO (0x40000000), / * SSO * / ; ACL_SS_ADMIN (0xc0000000), / * Security management right * / ; ACL_DBA (0x7fffff), / * DBA * / ; ACL_DBO (0xffffff); / * DBO * / 。

[0025] In this embodiment, it further includes an SQL editing and execution module. The SQL editing and execution module operates on database objects through an interface, specifically including: first, performing syntax parsing through an editor to parse the executed SQL input by the user in the editing box, mainly parsing line breaks; then sending the SQL to the Xugu database through JDBC and waiting for the database result to be returned, and displaying it in the result column. The data in the result column can be directly exported, and the export formats support txt.sql and csv.

[0026] In this embodiment, it further includes a backup and recovery module. The backup and recovery module performs backup and recovery through an interface, including at the library level, schema level, and table level.

[0027] In this embodiment, it further includes a scheduled job module. The scheduled job module sets scheduled jobs through an interface.

[0028] In this embodiment, it further includes an object DDL export module. The object DDL export module obtains the specified database object information through getMetaData of JDBC, and assembles the data into a complete executable DDL statement through parsing. For details, see Figure 3, the DDL export process is as follows: select mode, select object, export, end. During the export process, functions such as displaying the query plan, submitting a rollback transaction, converting the case of SQL, and setting the font size can be performed.

[0029] In this embodiment, it further includes a text data import and export module. The text data import and export module can specify a single table or multiple tables for data export. The export formats are txt, csv, and sql files. The delimiter or custom delimiter can be selected, as well as the line break character and whether a header is required. For text import, select the Text text file to be imported and configure the basic configuration items, including the number of fields, whether it ends at the end of the line, whether there are column names at the top, whether to skip blank lines, set the reference character, comment line, and import line. Select the user, table name, import columns, data type, and import method. The specific process of text export can be referred to Figure 4 , specifically including: select table, select columns, export column headers, fill in filtering information, select the export path, confirm, end.

[0030] In this embodiment, it further includes an SQL execution record module. The SQL execution record module is used to record the operations on the interface for users to view.

[0031] A database object management method is implemented based on the above-mentioned database object manager, including the following steps: S1: Create database objects; mainly implement the creation and modification of database objects, which include: libraries, schemas, tables, indexes, partitions, constraints, views, sequence values, stored procedures / functions, packages, users, roles, etc.

[0032] S2: Manage database objects; mainly implement viewing, modifying database objects, data operations, SQL editing, viewing table structures, importing and exporting table structures and table data.

[0033] S3: Maintain database objects; mainly implement table statistical analysis of database objects, index reconstruction, view compilation / modification, trigger compilation / modification, and stored procedure / function compilation.

[0034] The present invention supports the creation, modification, and deletion of objects such as libraries, schemas, tables, indexes, partitions, constraints, views, sequence values, stored procedures / functions, packages, users, roles, etc., and can display the DDL information of the objects. The present invention facilitates users to better use the database through interface operations. The operations on database objects can be executed through the interface, mainly realizing the creation and modification of database objects, the management of database objects, and the maintenance of database objects. It can also implement the connection management of multiple databases and realize the migration of table objects and data between homogeneous or heterogeneous databases.

[0035] For the foregoing embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited by the described action sequence, because according to this application, some steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to this application.

[0036] In the above embodiments, the basic principles, main features and advantages of the present invention are described. Those skilled in the art should understand that the present invention is not limited by the above embodiments. What is described in the above embodiments and the specification only illustrates the principles of the present invention. Without departing from the spirit and scope of the present invention, any modifications and changes made by those skilled in the art that do not depart from the spirit and scope of the present invention shall fall within the protection scope of the appended claims of the present invention.

Claims

1. A database object manager, characterized in that, The operations on database objects are realized through an interface design, including a database object creation module, a database object management module, and a database object maintenance module. Among them, The database object creation module is used to create and modify database objects, and the database objects include one or more of libraries, schemas, tables, indexes, partitions, constraints, views, sequence values, stored procedures, functions, packages, users, and roles; The database object management module is used to view, modify, perform data operations, edit SQL, view table structures, import and export table structures and table data; The database object maintenance module is used to perform table statistical analysis, index reconstruction, view compilation, modification, trigger compilation, modification, stored procedure, and function compilation on database objects.

2. The database object manager according to claim 1, characterized in that It also includes a database user permission display module, which intuitively displays the permissions owned by the user by mapping the user permission codes, and realizes the authorization of users when creating users or modifying the permissions of users subsequently.

3. A database object manager according to claim 1, characterized in that, It also includes an SQL editing and execution module, which operates on database objects through the interface. Specifically, it includes: parsing the syntax through an editor, parsing the executed SQL input by the user in the edit box, then sending the SQL to the database through JDBC, waiting for the database result to be returned, and displaying it in the result column.

4. A database object manager according to claim 1, characterized in that, It also includes a backup and recovery module, which performs backup and recovery through the interface, including library level, schema level, and table level.

5. A database object manager as claimed in claim 1, wherein It also includes a scheduled job module, which sets scheduled jobs through the interface.

6. The database object manager according to claim 1, wherein It also includes an object DDL export module, which obtains the specified database object information through getMetaData of JDBC and assembles the data into a complete executable DDL statement through parsing.

7. The database object manager according to claim 1, wherein It also includes a text data import and export module, which exports data by specifying single tables or multiple tables, and the export formats are txt, csv, and sql files.

8. The database object manager according to claim 1, wherein It also includes an SQL execution record module, which is used to record the operations on the interface for users to view.

9. A database object management method, implemented based on the database object manager according to any one of claims 1 to 8, characterized in that It includes the following steps: S1: Database object creation; S2: Database object management; S3: Database object maintenance.

Images