CN107480210B

CN107480210B - Memory data operation method and device

Info

Publication number: CN107480210B
Application number: CN201710621317.0A
Authority: CN
Inventors: 郑雄伟
Original assignee: Linkdood Technologies Sdn Bhd
Current assignee: Linkdood Technologies Sdn Bhd
Priority date: 2017-07-27
Filing date: 2017-07-27
Publication date: 2020-07-14
Anticipated expiration: 2037-07-27
Also published as: CN107480210A

Abstract

The invention provides a memory data operation method and a device, wherein the method comprises the following steps: establishing a database file of a memory database, and establishing connection between the memory database and an application program; packaging the database file and a pre-established database tool class into a class library; responding to a first operation request, loading the class library in an application program, and storing the memory data of the application program by using the database file; and responding to a second operation request, calling the database tool class, and executing the operation corresponding to the second operation request on the memory data in the database file.

Description

Memory data operation method and device

Technical Field

The invention relates to the technical field of data storage, in particular to a memory data operation method and device.

Background

At present, two processing methods for memory data (or micro data) mainly include the first method of directly storing the memory data into the memory, and the second method of serializing the memory data into a local file. Both of these two methods have certain disadvantages, and the first method is convenient for operating the memory data, but the memory data will be lost once the program is restarted or the device is down, and the memory data cannot be persistently stored. The second way can persistently store the memory data relative to the first way, but is inconvenient for data operation.

Disclosure of Invention

In view of the above, the present invention provides a method and an apparatus for operating memory data to improve the above problem.

In order to achieve the above object, an embodiment of the present invention provides a memory data operating method, where the method includes:

establishing a database file of a memory database, and establishing connection between the memory database and an application program;

packaging the database file and a pre-established database tool class into a class library;

responding to a first operation request, loading the class library in an application program, and storing the memory data of the application program by using the database file;

and responding to a second operation request, calling the database tool class, and executing the operation corresponding to the second operation request on the memory data in the database file.

Optionally, in the method, the step of establishing a connection between the in-memory database and the application program includes:

registering a driver for establishing database connection;

and loading the driver, and establishing the connection between the memory database and the application program based on the driver.

Optionally, in the above method, the in-memory database is an SQ L ite database.

Optionally, in the above method, the driver is org.

Optionally, in the above method, the in-memory database file is created by a cmd instruction or by an SQ L ite visualization management tool.

Optionally, in the above method, the database tool class includes a data add instruction, a data delete instruction, a data rewrite instruction, and a data query instruction.

An embodiment of the present invention further provides a memory data operating apparatus, where the apparatus includes:

the establishing module is used for establishing a database file of a memory database and establishing connection between the memory database and an application program;

the packaging module is used for packaging the database file and a pre-established database tool class into a class library;

the first operation module is used for responding to a first operation request, loading the class library in an application program and storing the memory data of the application program by using the memory database;

and the second operation module is used for responding to a second operation request, calling the database tool class and executing the operation corresponding to the second operation request on the memory data in the database file.

Optionally, in the above apparatus, the manner in which the establishing module establishes the connection between the in-memory database and the application program includes:

registering a driver for establishing database connection;

and loading the driver, and establishing the connection between the memory database file and the application program based on the driver.

Optionally, in the above apparatus, the in-memory database is an SQ L ite database.

Optionally, in the above apparatus, the driver is org.

According to the memory data operation method and device provided by the embodiment of the invention, the memory data of the application program is stored through the memory database, and the interface for operating the memory data is established on the basis of the memory database, so that the memory data stored in the memory database can be operated through the interface conveniently. Therefore, the memory data can be stored persistently, and the operation efficiency of the memory data is improved.

In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the solution of the embodiment of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is a part of the embodiment of the present invention, but not a whole embodiment. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 is a block diagram of an electronic device according to an embodiment of the present invention.

Fig. 2 is a flowchart illustrating a memory data operation method according to an embodiment of the present invention.

Fig. 3 is a schematic view of the substeps of step S110 shown in fig. 2.

Fig. 4 is a functional block diagram of a memory data operating apparatus according to an embodiment of the present invention.

Icon: 100-an electronic device; 110-memory data manipulation means; 111-building a module; 112-packaging the module; 113-a first operational module; 114-a second operational module; 120-a memory; 130-a processor.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.

Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.

As shown in fig. 1, which is a block diagram of an electronic device 100 according to an embodiment of the present invention, an application program is installed in the electronic device 100, and the memory data operation method and apparatus according to the embodiment of the present invention may be applied to the application program. The electronic device 100 includes a memory data operating device 110, a storage 120, and a processor 130.

The elements of the memory 120 and the processor 130 are electrically connected to each other directly or indirectly to realize data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The memory data operating device 110 includes at least one software functional module which can be stored in the memory 120 in the form of software or firmware (firmware) or is fixed in an Operating System (OS) of the electronic device 100.

The processor 130 is used for executing executable modules stored in the storage 120, such as software functional modules and computer programs included in the memory data operating device 110.

In this embodiment, the Memory 120 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like.

The processor 130 may be an integrated circuit chip having signal processing capabilities. The Processor 130 may also be a general-purpose Processor, such as a Central Processing Unit (CPU), a Network Processor (NP), etc.; but may also be a Digital Signal Processor (DSP)), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The processor 130 may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present invention. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should be understood that the configuration shown in FIG. 1 is merely illustrative and that electronic device 100 may have more or fewer components than shown in FIG. 1, or may have a different configuration than shown in FIG. 1. It should be noted that the components shown in fig. 1 can be implemented in software, hardware or a combination thereof.

Fig. 2 is a schematic flow chart of a memory data operation method according to an embodiment of the present invention, where the memory data operation method is applicable to an application program in the electronic device 100 shown in fig. 1, and is used for storing and operating memory data of the application program in the electronic device 100. In this embodiment, the electronic device 100 may be a JAVA-based electronic device, and the application program in the electronic device 100 may be a JAVA program.

The specific process and steps shown in fig. 2 will be described in detail below.

Step S110, a database file of the memory database is established, and a connection between the memory database and the application program is established.

In this embodiment, the in-memory database may be an SQ L ite database, and the SQ L ite database is a lightweight relational database, in the case of the SQ L ite database, a database file is a database, and the operation database is actually an operation on the database file.

Thus, establishing a connection between the in-memory database and the application program, which may also be referred to as establishing a database connection, is essentially to establish a data transmission channel between the in-memory database and the application program, so as to open the data transmission channel when the application program needs to operate data in the in-memory database. It should be understood that the database connection established in the present embodiment is not a connection between the in-memory database and a specific application, but a connection object (connection) that can be used to operate the in-memory database.

In this embodiment, when the memory database is SQ L ite, the connection between the memory database and the application program is established, that is, the connection between the SQ L ite database and the application program is established.

Optionally, in this embodiment, the database file may be created through a cmd command line, or may be created through an SQ L ite database visualization management tool.

Optionally, in this embodiment, the step of establishing the connection between the in-memory database and the application program in step S110 may be implemented by two substeps, namely step S111 and step S112.

Step S111, registers a driver for establishing a database connection.

In this embodiment, the driver may be org.sqlite.jdbc. it is to be noted that JDBC (Java database Connectivity) is a Java API (Application Programming Interface) for executing SQ L statement.

Before a database connection is established using the JDBC driver, the driver to be used needs to be registered in the driver manager. In this embodiment, the registered driver is org.sqlite.jdbc.

Step S112, loading the driver, and establishing a connection between the in-memory database and the application program based on the driver.

In the present embodiment, assuming that the database file established in step S110 is test.db, step S111 and step S112 may be implemented by the following codes:

String dbFilePath＝"test.db"；

Class.forName("org.sqlite.JDBC")；

connect＝DriverManager.getConnection("jdbc.sqlite；"+dbFilePath)。

forName ("org.sqlite.JDBC") is used to inform the electronic device 100 of the drivers that the database file test.db needs to be used. Drivermanager is used to handle the loading and unloading of JDBC drivers. Connection is used to establish a connection between the JAVA program and the in-memory database.

Furthermore, the input parameters of drivermanager getconnection () may include a database address (e.g., UR L address), a user name, and a password, where the database address corresponds to the selected database driver, and different database drivers have different addresses.

And step S120, packaging the database file and a pre-established database tool class into a class library.

In this embodiment, the database tool class may include a data adding instruction, a data deleting instruction, a data rewriting instruction, and a data querying instruction, and is used to add, delete, rewrite, or query the memory data in the memory database. In implementation, the instructions may be pre-written, and the written instructions may be packaged into a tool class (Utils), that is, the database tool class.

In this embodiment, the database file and the database tool class are packaged into a class library (jar package).

Step S130, in response to the first operation request, loading the class library in the application program, and storing the memory data of the application program using the memory database.

In implementation, the jar packet can be loaded in a corresponding application program when the memory database is needed to store the memory data. The first operation request refers to an operation request that requires use of the in-memory database.

Step S140, responding to a second operation request, calling the database tool class, and executing an operation corresponding to the second operation request on the memory data in the memory database.

In this embodiment, if an operation needs to be performed on the memory database, for example, the memory data in the memory database needs to be added, deleted, checked, or changed, the database tool class may be called, and the operation corresponding to the second operation request may be executed through a corresponding instruction in the database tool class.

The second operation request refers to an SQ L statement, the SQ L statement is used for requesting at least one of memory data addition, memory data deletion, memory data modification and memory data query, in implementation, if the SQ L statement is used for requesting memory data addition, a data addition instruction in the database tool class is called, and if the SQ L statement is used for requesting memory data deletion, a data deletion instruction in the database tool class is called.

As shown in fig. 4, the embodiment of the present invention further provides a memory data operating device 110. The memory data operation device 110 includes a setup module 111, a packaging module 112, a first operation module 113, and a second operation module 114.

The establishing module 111 is configured to establish a data file of a memory database, and establish a connection between the memory data and an application program.

In this embodiment, the detailed description of the step S110 shown in fig. 2 may be referred to for the description of the establishing module 111. That is, the step S110 may be performed by the establishing module 111.

Optionally, in this embodiment, the establishing module 111 may establish the connection between the database file and the in-memory database in the following manner:

registering a driver for establishing database connection, loading the driver, and establishing connection between the memory database and an application program based on the driver.

Optionally, in this embodiment, the in-memory database may be an SQ L ite database.

Optionally, in this embodiment, the driver may be org.sqlite.jdbc.

The packaging module 112 is configured to package the database file and a pre-established database tool class into a class library.

In this embodiment, the description of the encapsulation module 112 may specifically refer to the detailed description of the step S120 shown in fig. 2, that is, the step S120 may be executed by the encapsulation module 112.

The first operation module 113 is configured to load the class library in an application program in response to a first operation request, and store the memory data of the application program using the memory database.

In this embodiment, the description of the first operation module 113 may specifically refer to the detailed description of the step S130 shown in fig. 2, that is, the step S130 may be executed by the first operation module 113.

The second operation module 114 is configured to respond to a second operation request, invoke the database tool class, and execute an operation corresponding to the second operation request on the memory data in the database file.

In this embodiment, the description of the second operation module 114 may specifically refer to the detailed description of step S140 shown in fig. 2, that is, step S140 may be executed by the second operation module 114.

In summary, the memory data operation method and apparatus provided in the embodiments of the present invention store the memory data of the application program through the memory database, and establish an interface for operating the memory data based on the memory database, so as to facilitate the operation of the memory data stored in the memory database through the interface. Therefore, the memory data can be stored persistently, and the operation efficiency of the memory data is improved.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In addition, the functional modules in the embodiments of the present invention may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for operating on memory data, the method comprising:

responding to a first operation request, loading the class library in an application program, and storing the memory data of the application program by using the database file, wherein the first operation request refers to an operation request needing to use a memory database;

and responding to a second operation request, calling the database tool class, and executing an operation corresponding to the second operation request on the memory data in the database file, wherein the second operation request refers to an SQ L statement, and the SQ L statement is used for requesting at least one of memory data addition, memory data deletion, memory data modification and memory data query.

2. The method of claim 1, wherein the step of establishing a connection between the in-memory database and an application comprises:

registering a driver for establishing database connection;

3. The method of claim 2, wherein the in-memory database is a SQ L ite database.

4. The method of claim 3, wherein the driver is org.

5. The method as claimed in claim 3, wherein the in-memory database file is created by cmd commands or by SQ L ite visualization management tool.

6. The method according to any one of claims 1 to 5, wherein the database tool class comprises a data adding instruction, a data deleting instruction, a data rewriting instruction and a data querying instruction.

7. A memory data manipulation device, the device comprising:

the first operation module is used for responding to a first operation request, loading the class library in an application program, and storing the memory data of the application program by using the memory database, wherein the first operation request refers to an operation request needing to use the memory database;

the second operation module is configured to invoke the database tool class in response to a second operation request, and perform an operation corresponding to the second operation request on the memory data in the database file, where the second operation request is an SQ L statement, and the SQ L statement is used to request at least one of adding memory data, deleting memory data, modifying memory data, and querying memory data.

8. The apparatus of claim 7, wherein the means for establishing the connection between the database file and the in-memory database comprises:

registering a driver for establishing database connection;

9. The apparatus of claim 8, wherein the in-memory database is a SQ L ite database.

10. The apparatus of claim 9, wherein the driver is org.sqlite.JDBC.