CN106407404A - A data storage method, a data management method and system, a database and a client - Google Patents
A data storage method, a data management method and system, a database and a client Download PDFInfo
- Publication number
- CN106407404A CN106407404A CN201610841153.8A CN201610841153A CN106407404A CN 106407404 A CN106407404 A CN 106407404A CN 201610841153 A CN201610841153 A CN 201610841153A CN 106407404 A CN106407404 A CN 106407404A
- Authority
- CN
- China
- Prior art keywords
- database table
- field
- target
- data
- metadata
- 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
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/23—Updating
- G06F16/235—Update request formulation
-
- 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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
Abstract
The invention provides a data storage method, a data management method and system, a database and a client. The data storage method comprises the steps of S0: establishing a database table in a database, setting identifier information corresponding to the database table and establishing a field comment table corresponding to the database table; S1: storing at least one piece of metadata by using the database table; S2: storing field comment information of the database table by using the field comment table, wherein the field comment information includes the code table corresponding to each field of the database table and each code table records the mapping relationship between at least one rendering parameter and at least one piece of metadata. According to the technical solution, when a client renders and displays metadata in a database table, even the database table is frequently updated, there is no need to update the client frequently, so that the user experience is improved.
Description
Technical field
The present invention relates to areas of information technology, it is specifically designed a kind of date storage method, data managing method and system, number
According to storehouse, client.
Background technology
With the continuous development of information technology, information category also increasingly numerous and complicated, the business of corresponding difference information categories
Data also increases in a large number, and most enterprises or organization need store its business datum, meanwhile, part in data base using data base
Database table is also frequently necessary to show to user.
At present, when being shown for wide area information server table, it usually needs client is customized melt and sends out,
It is directed to each database table in the client and be respectively provided with corresponding displaying rule, to render and to show according to this displaying rule
Show the business datum under specific field in database table.
But, in technique scheme, when database table has frequent updating, such as frequently new in database table
When increasing field or changing metadata under the existing field of database table, then need frequent updating client, Consumer's Experience is relatively
Difference.
Content of the invention
Embodiments provide a kind of date storage method, data managing method and system, data base, client,
Consumer's Experience can be improved.
In a first aspect, embodiments providing a kind of date storage method, including：
S0：Build database table in data base, the corresponding identification information of described database table is set；Build corresponding described
The field annotation table of database table；Also include：
S1：Store at least one metadata using described database table；
S2：Store the field annotation information of described database table using described field annotation table；Wherein, described field annotation
Information includes each field corresponding code table respectively of described database table, and described code table record has at least one rendering parameter
Mapping relations and at least one metadata between.
Preferably, also include：
Build the form annotation table of corresponding described database table；Store described database table using described form annotation table
Form annotation information；Wherein, the designated separators of described form annotation information become at least two chunk；
And/or,
Build the Major key table of corresponding described database table；Store each of described database table using described Major key table
Individual field corresponding Major key respectively.
Preferably,
When storing the field annotation information of described database table using described field annotation table, if same described code
In table, record has the mapping relations between at least two rendering parameter and at least two metadata, then using specified separators
Each described metadata corresponding mapping relations respectively.
Second aspect, embodiments provides a kind of data base, including：
Database table, and the field annotation table of corresponding described database table；Wherein,
Described database table, for storing at least one metadata；
Described field annotation table, for storing the field annotation information of uncle's database table；Wherein, described field annotation letter
Breath includes each field respectively corresponding code table of described database table, described code table record have at least one rendering parameter and
Mapping relations between at least one metadata.
Preferably,
Also include：The form annotation table of corresponding described database table, and/or, the Major key table of corresponding described database table；
Wherein,
Described form annotation table, for storing the form annotation information of described database table；Wherein, described form annotation letter
Breath is designated separators and becomes at least two chunk；
Described Major key table, for storing each field corresponding Major key respectively of described database table.
The third aspect, embodiments provides a kind of data managing method, is applied in client, including：
Obtain the identification information of target database table, send the data acquisition carrying described identification information to service middleware
Request；
Receive the data structure of the described target database table that service middleware obtains according to described identification information and forwards
And field annotation information；
Parse described field annotation information to obtain each field corresponding code table respectively of described target database table,
Wherein, described code table record has the mapping relations between at least one rendering parameter and at least one metadata；
According to the mapping relations recording respectively in each described code table, replace institute using at least one rendering parameter described
State in data structure corresponding metadata to form first object data structure；
Form and show the first displaying form of corresponding described database table according to described first object data structure.
Preferably,
The described data receiving the described target database table that service middleware obtains according to described identification information and forwards
Structure and field annotation information, further include：Receive service middleware to be obtained and described in forwarding according to described identification information
The form annotation information of target database table；The described field annotation information of described parsing is to obtain the every of described target database table
One field corresponding code table respectively, further includes：Parse described form annotation information, to determine described form annotation information
In be designated separators at least two chunk；Described formed and show correspondence according to described first object data structure
First displaying form of described target database table, further includes：Show each described information block；
And/or,
The described data receiving the described target database table that service middleware obtains according to described identification information and forwards
Structure and field annotation information, further include：Receive service middleware to be obtained and described in forwarding according to described identification information
Each field of target database table corresponding Major key respectively；
In described the first exhibition being formed according to described first object data structure and showing corresponding described target database table
After showing form, also include：
Receive code table operational order, wherein, described code table operational order carries target Major key and operation strategy；
Determine the corresponding aiming field of described target Major key, and determine described aiming field corresponding target code table；
According to described operation strategy, the mapping relations of record in described target code table are processed accordingly；
According to the mapping relations of record in the described target code table after processing, it is right in described first object data structure to update
The target metadata answering described aiming field is to form the second target data structure；
Form and show the second displaying form of corresponding described target database table according to described second target data structure.
Fourth aspect, embodiments provides a kind of client, including：
Request of data unit, for obtaining the identification information of target database table, sends to service middleware described in carrying
The data acquisition request of identification information；
Data receipt unit, for receiving the described number of targets that service middleware obtains according to described identification information and forwards
Data structure and field annotation information according to storehouse table；
Data resolution unit, for parsing described field annotation information to obtain each word of described target database table
Section corresponding code table respectively, wherein, described code table record has reflecting between at least one rendering parameter and at least one metadata
Penetrate relation；
Data mapping unit, for according to the mapping relations recording respectively in each described code table, using described at least
In one rendering parameter described data structure of replacement, corresponding metadata is to form first object data structure；
Display processing unit, for forming according to described first object data structure and showing corresponding described database table
First displaying form.
Preferably,
Described data receipt unit, is further used for receiving what service middleware obtained according to described identification information and forwarded
The form annotation information of described target database table；
Described data resolution unit, is further used for parsing described form annotation information, to determine described form annotation letter
It is designated at least two chunk of separators in breath；
Described display processing unit, is further used for showing each described information block；
And/or,
Also include：Instruction reception unit, determining unit, code table processing unit；Wherein,
Described data receipt unit, is further used for receiving what service middleware obtained according to described identification information and forwarded
Each field of described target database table corresponding Major key respectively；
Described instruction reception unit, for receiving code table operational order, wherein, described code table operational order carries target master
Key assignments and operation strategy；
Described determining unit, for determining the corresponding aiming field of described target Major key, and determines described target word
The corresponding target code table of section；
Described code table processing unit, for entering to the mapping relations of record in described target code table according to described operation strategy
Row is corresponding to be processed；
Described data mapping unit, is further used for the mapping relations according to record in the described target code table after processing,
The target metadata updating corresponding described aiming field in described first object data structure is to form the second target data structure；
Described display processing unit, is further used for being formed according to described second target data structure and showing described in correspondence
Second displaying form of target database table.
5th aspect, embodiments provides a kind of data management system, including：
Service middleware, as described data base arbitrary in above-mentioned second aspect, and as arbitrary in above-mentioned fourth aspect
Described client；Wherein,
Described service middleware, for receiving the number of the identification information carrying target database table that described client sends
Ask according to obtaining；According to the data structure of target database table in the described identification information described data base of acquisition and correspondence
The field annotation information of target database table, and it is forwarded to described client.
Embodiments provide a kind of date storage method, data managing method and system, data base, client,
By in data base build database table store at least one metadata, build simultaneously to should database table field note
Release table to store the field annotation information of this database table, each field that field information includes database table is corresponding respectively
Code table, have recorded the mapping relations between at least one rendering parameter and at least one metadata in code table；Accordingly, by
In data base build correspondence database table field annotation table, with metadata under each field of data storage storehouse table with render ginseng
Mapping relations between number, when under there is client and needing to database table, the metadata of storage is rendered and shows, then
Mapping relations between respective meta-data and rendering parameter can be obtained according to field annotation table it is not necessary to frequent updating client, can
Improve Consumer's Experience.
Brief description
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, below will be to embodiment or existing
Have technology description in required use accompanying drawing be briefly described it should be apparent that, drawings in the following description are the present invention
Some embodiments, for those of ordinary skill in the art, on the premise of not paying creative work, can also basis
These accompanying drawings obtain other accompanying drawings.
Fig. 1 is a kind of flow chart of date storage method that one embodiment of the invention provides；
Fig. 2 is a kind of structural representation of data base that one embodiment of the invention provides；
Fig. 3 is the structural representation of another kind of data base that one embodiment of the invention provides；
Fig. 4 is a kind of flow chart of data managing method that one embodiment of the invention provides；
Fig. 5 is a kind of structural representation of client that one embodiment of the invention provides；
Fig. 6 is the structural representation of another kind of client that one embodiment of the invention provides；
Fig. 7 is a kind of structural representation of data management system that one embodiment of the invention provides；
Fig. 8 is the flow chart of another kind of data managing method that one embodiment of the invention provides.
Specific embodiment
Purpose, technical scheme and advantage for making the embodiment of the present invention are clearer, below in conjunction with the embodiment of the present invention
In accompanying drawing, the technical scheme in the embodiment of the present invention is clearly and completely described it is clear that described embodiment is
The a part of embodiment of the present invention, rather than whole embodiments, based on the embodiment in the present invention, those of ordinary skill in the art
The every other embodiment being obtained on the premise of not making creative work, broadly falls into the scope of protection of the invention.
As shown in figure 1, embodiments providing a kind of date storage method, including：
S0：Build database table in data base, the corresponding identification information of described database table is set；Build corresponding described
The field annotation table of database table；Also include：
S1：Store at least one metadata using described database table；
S2：Store the field annotation information of described database table using described field annotation table；Wherein, described field annotation
Information includes each field corresponding code table respectively of described database table, and described code table record has at least one rendering parameter
Mapping relations and at least one metadata between.
In the above embodiment of the present invention, store at least one metadata by building database table in data base, with
When build to should database table the field annotation information to store this database table for the field annotation table, field information includes counting
According to each field corresponding code table respectively of storehouse table, in code table, have recorded at least one rendering parameter and at least one metadata
Between mapping relations；Accordingly, by building the field annotation table of correspondence database table in data base, with data storage storehouse
Mapping relations between metadata and rendering parameter under each field of table, store under client needs to database table when existing
Metadata when being rendered and showing, then can obtain the mapping between respective meta-data and rendering parameter according to field annotation table
Relation, it is not necessary to frequent updating client, can improve Consumer's Experience.
It should be appreciated that field annotation information can also include each field name corresponding wash with watercolours respectively of database table
Dye parameter.
In the above embodiment of the present invention, there may be due under the more and different field of the field quantity of database table
Identical metadata, but the same metadata under different field characterizes different meanings in database table respectively, i.e. identical unit
Data under the different field of same database table respectively corresponding rendering parameter may and differ, for example, data
When storehouse table includes field " sex " and field " age ", under field " sex ", record has metadata " 1 " and metadata " 2 ", word
Metadata " 1 " under section " sex " can correspond to rendering parameter " male ", and metadata " 2 " can correspond to rendering parameter " female ", in field " year
Under age ", record has metadata " 1 ", " 2 " and " 3 ", and the metadata " 1 " under field " age " can correspond to rendering parameter " less than 18
In year ", metadata " 2 " can correspond to rendering parameter " more than 18 and less than 50 years old ", and metadata " 3 " can correspond to rendering parameter and " be not less than
50 years old ", now, in order to enable the client to using different rendering parameter accurately for identical under different field in database table
Metadata rendered respectively, can be by different code tables come under respectively record field " sex " and field " age " at least one
Mapping relations between individual metadata and at least one rendering parameter.
In a preferred embodiment of the invention, under each field of database table, substantial amounts of metadata can be recorded respectively,
In the corresponding code table respectively of each field using field annotation table data storage storehouse table, the data volume in field annotation table
Also just relatively large, for convenience the data in field annotation table is managed, in field annotation table, can be utilized different
Data-base recording distinguishes corresponding code table each field to distinguish database of record table.
Accordingly, in same data-base recording, then may need to record multiple metadata and multiple rendering parameter it
Between mapping relations, at this time, it may be necessary to be directed to many between multiple metadata and multiple rendering parameter using unified definition mode
Group mapping relations are defined respectively；Specifically, in a preferred embodiment of the invention, using the storage of described field annotation table
During the field annotation information of described database table, if there are at least two rendering parameter and at least two in same described code table
Mapping relations between individual metadata, then using specifying each described metadata of separators, corresponding mapping is closed respectively
System.
For example, under the field " sex " of database table, record has metadata " 1 " and metadata " 2 ", and metadata " 1 " is right
Answer rendering parameter " male ", the corresponding rendering parameter " female " of metadata " 2 ", then, the corresponding code table of field " sex " of database table
Data-base recording in field annotation table can be " 1 | man, 2 | female ", this data storehouse record ", " for specify separator.
It should be appreciated that each field name of database table corresponding rendering parameter when client is shown also may be used
It is stored in field annotation table, for example, the field name " x " of database table characterizes sex, the corresponding code table of field " x " can be remembered
Record for " 1 | man, 2 | female ", now, record in the data-base recording of current code table, can before code table record field name " x " corresponding
Rendering parameter " sex ", now, this data storehouse record then be " sex, 1 | man, 2 | female "；Client parsing field annotation letter
During breath, the character string before code table can be defaulted as the field name of the corresponding field of current code table when client is shown
Rendering parameter.Certainly, in the record of each data storehouse, between the corresponding rendering parameter of field name and code table, it can also be set
His flag parameters, such as this data storehouse is recorded as " sex, code table：1 | man, 2 | female ", wherein " code table " then can join as labelling
Number, during client parsing field annotation information, the Chinese character " sex " before " code table " then can be defaulted as present field
Corresponding rendering parameter.
Further, client obtains the other information of simultaneously video data storehouse table, such as current database table for convenience
Build the time, build the form annotation information such as the user name of current database table, the effect duration of current database table, the present invention
In one preferred embodiment, also include：Build the form annotation table of corresponding described database table；Deposited using described form annotation table
Store up the form annotation information of described database table；Wherein, the designated separators of described form annotation information become at least two
Chunk.
In the above embodiment of the present invention, client render and display data storehouse table in metadata when, can be simultaneously from right
Corresponding form annotation information should be obtained in the form annotation table of database table, be processed accordingly in client and open up
Show.
In the above embodiment of the present invention, in the form data of database table storage, can be according to information category using specified point
Every symbol, form annotation information is separated into multiple chunk, client when showing form annotation information, then can be shown each respectively
Individual chunk, so that the content intuitivism apprehension form annotation information that user shows soon respectively according to each information；For example, number
Form annotation table recordable form annotation information according to storehouse table is " title：Statistics forecast of sales, director：Zhang San ", its
In, ", " in form annotation information is for specifying separator.
It should be noted that specifying separator can also be other forms, such as：/, | etc..
Further, client is directed to the different field of database table the reflecting of record in corresponding code table respectively for convenience
Relation of penetrating is processed accordingly, such as deletes, changes or increases between at least one rendering parameter and at least one metadata
Mapping relations etc., in a preferred embodiment of the invention, also include：Build the Major key table of corresponding described database table；Profit
Store each field corresponding Major key respectively of described database table with described Major key table.
So, user can be operated in client terminal device according to aiming field corresponding target Major key using corresponding
Strategy is processed accordingly for the aiming field corresponding target code table of database table, so that client terminal device is by data base
Respective meta-data in table is updated to User Defined rendering parameter and shows after forming corresponding displaying form.
As shown in Fig. 2 embodiments providing a kind of data base, including：
Database table 201, and the field annotation table 202 of corresponding described database table 201；Wherein,
Described database table 201, for storing at least one metadata；
Described field annotation table 202, for storing the field annotation information of described database table 201；Wherein, described field
Annotation information includes each field corresponding code table respectively of described database table 201, and described code table record has at least one
Mapping relations between rendering parameter and at least one metadata.
The field of current database table in the above embodiment of the present invention, is stored using the field annotation table of correspondence database table
Annotation information, when the metadata under there is client and needing to database table is rendered and shows, client then can basis
In field annotation table, the field annotation information of storage obtains the mapping relations between respective meta-data and rendering parameter, even if data
When there is new field or newly-increased metadata under the table of storehouse, corresponding more newer field annotation table, staff is not necessarily referring to client
End device is updated accordingly, then can be utilized client terminal device the metadata in database table to be rendered accordingly and opens up
Show, user's summary is preferable.
As shown in figure 3, in a preferred embodiment of the invention, also including：The form annotation of corresponding described database table 201
Table 301, and/or, the Major key table 302 of corresponding described database table 201；Wherein,
Described form annotation table 301, for storing the form annotation information of described database table 201；Wherein, described form
Annotation information is designated separators and becomes at least two chunk；
Described Major key table 302, for storing each field corresponding Major key respectively of described database table 201.
In the above embodiment of the present invention, need to carry out accordingly for the metadata in database table when there is client terminal device
When rendering and showing, each field of form annotation information and database table can be obtained from form annotation table respectively simultaneously
Corresponding Major key, the display mode display form annotation information that client terminal device can be specified；Meanwhile, client terminal device also may be used
So that according to aiming field corresponding target Major key, the aiming field being directed to database table using corresponding operation strategy is corresponding
Target code table is processed accordingly, so that client terminal device is by corresponding for the respective meta-data in database table rendering parameter more
It is newly User Defined rendering parameter, and form corresponding displaying form to show.
As shown in figure 4, embodiments providing a kind of data managing method, it is applied in client, including：
Step 401, obtains the identification information of target database table, sends to service middleware and carries described identification information
Data acquisition request；
Step 402, receives the described target database table that service middleware obtains according to described identification information and forwards
Data structure and field annotation information；
Step 403, each field parsing described field annotation information to obtain described target database table is right respectively
The code table answered, wherein, described code table record has the mapping relations between at least one rendering parameter and at least one metadata；
Step 404, according to the mapping relations recording respectively in each described code table, using described at least one render ginseng
In the number described data structure of replacement, corresponding metadata is to form first object data structure；
Step 405, forms and shows the first displaying of corresponding described database table according to described first object data structure
Form.
In the above embodiment of the present invention, when client is rendered and is shown for the metadata under target database table,
Only need to provide the identification information of target database table to service middleware, you can make service middleware be obtained according to this identification information
Take and forward the data structure of target database table and its corresponding field annotation information, by parsing is carried out to annotation information be
Each field corresponding code table respectively in target database table, and then at least one unit according to record in each code table can be obtained
Mapping relations between data and at least one rendering parameter, using corresponding at least one rendering parameter replacement data structure
Metadata can form the first data structure, can be formed according to this first data structure and show corresponding target database table
First displaying form；As fully visible, client terminal device is obtained accordingly by the field annotation information obtaining target database table
Mapping relations between metadata and rendering parameter, even if target database table has renewal, are also not necessarily referring to client dress
Put to be customized melting and send out with the mapping relations between typing respective meta-data and rendering parameter, it is to avoid frequent updating client,
Consumer's Experience can be improved.
It should be appreciated that during client parsing field annotation information, each word of database table can also be got
Section name corresponding rendering parameter respectively, can also be using the field of database table in corresponding rendering parameter replacement data structure
Name, and then realize the field name of database table is rendered and shows.
In the above embodiment of the present invention, identification information can be storage address in data base for the target database table or table
Lattice title etc., this table identification information should carry out unique mark to the target database table in data base, and makes service
Middleware can be according to this unique mark access target database table.
In a preferred embodiment of the invention, described reception service middleware obtains according to described identification information and forwards
The data structure of described target database table and field annotation information, further include：Receive service middleware according to described mark
Know the form annotation information of acquisition of information the described target database table forwarding；
Described each field parsing described field annotation information to obtain described target database table is corresponding respectively
Code table, further includes：Parse described form annotation information, be designated separators in described form annotation information to determine
At least two chunk；
Described the first displaying being formed according to described first object data structure and showing corresponding described target database table
Form, further includes：Show each described information block.
In the above embodiment of the present invention, when client is rendered and is shown for the metadata under target database table,
Form data (title of such as database table, director and the effect duration of simultaneously display data storehouse table can be obtained simultaneously
Deng)；Client terminal device, according to the organizational structure of form annotation information, shows each information being designated separators respectively
Block, is easy to the content that user intuitively understands each chunk.
In a preferred embodiment of the invention, described reception service middleware obtains according to described identification information and forwards
The data structure of described target database table and field annotation information, further include：Receive service middleware according to described mark
Know each field corresponding Major key respectively of acquisition of information the described target database table forwarding；
In described the first exhibition being formed according to described first object data structure and showing corresponding described target database table
After showing form, also include：
Receive code table operational order, wherein, described code table operational order carries target Major key and operation strategy；
Determine the corresponding aiming field of described target Major key, and determine described aiming field corresponding target code table；
According to described operation strategy, the mapping relations of record in described target code table are processed accordingly；
According to the mapping relations of record in the described target code table after processing, it is right in described first object data structure to update
The target metadata answering described aiming field is to form the second target data structure；
Form and show the second displaying form of corresponding described target database table according to described second target data structure.
In the above embodiment of the present invention, client render and display data storehouse table in metadata when, can be simultaneously from right
Each field corresponding Major key respectively should be obtained, accordingly, user can be according to reality in the Major key table of front database table
Border business demand, carries out self-defined modification for the metadata under database table in the display mode of client terminal device, specifically,
Client can be made to obtain target Major key, determine to should target Major key aiming field, and the corresponding mesh of aiming field
Coding table, so increased newly in target code table according to corresponding operation strategy, be deleted or modified at least one metadata with least
Mapping relations between one rendering parameter, and then first object data structure is updated to become into second according to amended code table
Data structure, you can form and show the second displaying form of corresponding target database table according to the second data structure.
As shown in figure 5, embodiments providing a kind of client, including：
Request of data unit 501, for obtaining the identification information of target database table, sends to service middleware and carries institute
State the data acquisition request of identification information；
Data receipt unit 502, for receiving the described mesh that service middleware obtains according to described identification information and forwards
The data structure of mark database table and field annotation information；
Data resolution unit 503, for parsing described field annotation information to obtain each of described target database table
Individual field corresponding code table respectively, wherein, described code table record has between at least one rendering parameter and at least one metadata
Mapping relations；
Data mapping unit 504, for according to the mapping relations recording respectively in each described code table, using described extremely
In a few rendering parameter described data structure of replacement, corresponding metadata is to form first object data structure；
Display processing unit 505, for forming according to described first object data structure and showing corresponding described data base
First displaying form of table.
In a preferred embodiment of the invention, described data receipt unit 502, it is further used for receiving service middleware root
The form annotation information of the described database table obtaining according to described identification information and forwarding；
Described data resolution unit 503, is further used for parsing described form annotation information, to determine described form annotation
It is designated at least two chunk of separators in information；
Described display processing unit 505, is further used for showing each described information block.
As shown in fig. 6, in a preferred embodiment of the invention, also including：Instruction reception unit 601, determining unit 602,
Code table processing unit 603；Wherein,
Described data receipt unit 502, is further used for reception service middleware and is obtained according to described identification information and turn
Each field of the described target database table sent out corresponding Major key respectively；
Described instruction reception unit 601, for receiving code table operational order, wherein, described code table operational order carries mesh
Mark Major key and operation strategy；
Described determining unit 602, for determining the corresponding aiming field of described target Major key, and determines described target
Field corresponding target code table；
Described code table processing unit 603, for closing to the mapping of record in described target code table according to described operation strategy
System is processed accordingly；
Described data mapping unit 504, is further used for being closed according to the mapping of record in the described target code table after processing
System, the target metadata updating corresponding described aiming field in described first object data structure is to form the second target data knot
Structure；
Described display processing unit 505, is further used for being formed and showing correspondence according to described second target data structure
Second displaying form of described target database table.
As shown in fig. 7, embodiments providing a kind of data management system, including：
Service middleware 701, such as described data base 702 arbitrary in above-described embodiment and as arbitrary in above-described embodiment
Described client 703；Wherein,
Described service middleware 701, for receiving the mark letter carrying target database table that described client 703 sends
The data acquisition request of breath；According to described identification information obtain described data base 702 in target database table data structure with
And the field annotation information of the described target database table of correspondence, and it is forwarded to described client 703.
As shown in figure 8, embodiments providing a kind of data managing method, with reference in the above embodiment of the present invention
Described data management system is realized utilizing database purchase metadata, and realizes obtaining by service middleware using client
The metadata of storage in database table, and as a example respective meta-data is rendered and shows, the method can include each as follows
Individual step.
Step 801, build in data base database table, to should database table field annotation table, to should data
The form annotation table of storehouse table, to should database table Major key table and setting database table identification information.
Here, identification information can be the address information in data base of title or database table of database table.
Step 802, stores at least one metadata using database table, using the word of field annotation table data storage storehouse table
Section annotation information, using form annotation table data storage storehouse table form annotation information, utilize Major key table data storage storehouse table
Each field respectively corresponding Major key.
In the embodiment of the present invention, field annotation information include each field of database table respectively corresponding code table and
Each field name corresponding rendering parameter respectively, each code table can take a data storehouse record in field annotation table；
In the code table of each data storehouse record, close when there is the mapping between at least two metadata and at least two rendering parameter
When being, using each metadata of specified separators corresponding mapping relations respectively.
In the embodiment of the present invention, in form annotation table, can be utilized and specify separator by inhomogeneity in form annotation information
Other message spacing is multiple chunk, and such as, the form annotation information that form annotates table record can include：" title：
Summary, director：Little red ", ", " is then to specify separator it is intended that form annotation information is divided into two by separator ", "
Individual chunk " title：Summary " and " director：Little red ".
In the embodiment of the present invention, corresponding Major key is each of database table to each field of database table respectively
Individual field name corresponding eigenvalue respectively, such as each field name corresponding digest value respectively.
For example, database table can include a summary, including field " name " field " x " and field
" level ", wherein field " name " characterize examinee's name, and field " x " characterizes sex, and field " level " characterizes the score of the examination；With
As a example the achievement of three examinees of data base table recording, database table as shown in table 1 below can be formed：
Table 1
| Name | X | Level |
| King two | 1 | 1 |
| Zhang San | 2 | 2 |
| Li Si | 1 | 3 |
Wherein, metadata " 1 " sign " male " under the field " x " of database table shown in table 1, " 2 " sign " female "；Field
Metadata " 1 " sign " outstanding " under " level ", metadata " 2 " sign " qualified ", metadata " 3 " are unqualified.
So, can be formed using the field annotation information of the field annotation table data storage storehouse table of this database table as follows
Form annotation table shown in table 2：
Table 2
| Field name | Spatial cue |
| Name | Name, null |
| X | Sex, 1 | man, 2 | female |
| Level | The score of the examination, 1 | outstanding, 2 | qualified, 3 | unqualified |
Wherein, in table 2, null characterizes the corresponding code table of field name is sky, that is, be not under name field in database table
Metadata rendered.
Step 803, client obtains the identification information of database table, sends to service middleware and carries this identification information
Data acquisition request.
Step 804, service middleware accesses data base according to identification information, to obtain the data structure of database table, from
Obtain the field annotation information of database table in field annotation table, obtain the form annotation letter of database table from form annotation table
Breath, obtains each field corresponding Major key respectively of database table from Major key table, and is forwarded to client.
Step 805, the data structure of client receiving data storehouse table, field annotation information, form annotation information and every
One field corresponding Major key respectively.
Step 806, client parses field annotation information to obtain each field corresponding code respectively of database table
Table and the corresponding rendering parameter of present field, parsing form annotation information is to determine at least two chunk.
For example, by parsing to the field annotation information obtaining, can obtain that field " name " is corresponding to be rendered
Parameter is " name ", and code table is sky；Obtaining field " x " corresponding rendering parameter is " sex ", code table be " 1 | man, 2 | female "；Obtain
Take the corresponding rendering parameter of field " level " be " score of the examination ", code table be " 1 | outstanding, 2 | qualified, 3 | unqualified ".
Here, it is respectively it may also be determined that going out corresponding two chunk of form annotation information：" title：Achievement is united
Meter table " and " director：Little red ".
Step 807, according to each field corresponding code table respectively, using word corresponding in rendering parameter replacement data structure
Section metadata, and in rendering data structure respective field field name, to form first object data structure.
For example, with row prioritized data queueing discipline, the data structure that can obtain database table is：[(name, king two,
Zhang San, Li Si), (x, 1,2,1), (level, 1,2,3)], using the mapping relations recording respectively in each code table to data
Metadata in structure is replaced, and using the field name in corresponding rendering parameter replacement data structure, can get the
One target data structure is：[(name, king two, Zhang San, Li Si), (sex, man, female, man), (score of the examination, outstanding, qualified,
Unqualified)].
Step 808, client forms according to first object data structure and shows the first displaying form, and display is each
Individual chunk.
Step 809, client receives the code table operational order carrying target Major key and operation strategy.
Step 810, client determine to should target Major key aiming field, and determine that this aiming field is corresponding
Target code table.
Step 811, client is processed for target code table accordingly according to this operation strategy.
Wherein, operation strategy includes increasing, the reflecting of at least one rendering parameter and at least one metadata is deleted or modified
Penetrate relation.
For example, when target Major key is the eigenvalue of field level, you can determine that aiming field is " level ", mesh
The corresponding target code table of marking-up section " level " is：" 1 | outstanding, 2 | qualified, 3 | unqualified ", operation strategy is modification target code table
Mapping relations between middle metadata " 1 " and rendering parameter " outstanding " are revised as " 1 | qualified ", then carry out phase to target code table
Should can get after processing code table " 1 | qualified, 2 | qualified, 3 | unqualified ".
Step 812, client updates the first data structure to form the second data structure according to the target code table after processing.
Accordingly, using process after code table " 1 | qualified, 2 | qualified, 3 | unqualified " update first object data structure
[(name, king two, Zhang San, Li Si), (sex, man, female, man), (score of the examination, outstanding, qualified, unqualified)], can form
Two target data structures [(name, king two, Zhang San, Li Si), (sex, man, female, man), (score of the examination, qualified, qualified, do not conform to
Lattice)].
It can be seen that, in step 809 to step 812, user can be in conjunction with practical business demand, for the respective field of database table
Under metadata display rule carry out self-defined rendering and showing.
Step 813, client according to formed the second data structure formed and show to should database table second exhibition
Show form, and show each chunk.
As fully visible, the embodiment of the present invention stores corresponding metadata by database table, builds in data base simultaneously
Field annotation table, the form annotation table and Major key table field annotation information of data storage storehouse table, form annotation information respectively
Each field of database table corresponding Major key respectively, when updating the data storehouse table, updates the data storehouse in data base
During table it is only necessary to simultaneously in more newer field annotation table record field annotation information, be directed in database table in client and store
Metadata when being rendered and showing, staff need not customized development client, it is to avoid frequent updating client, can carry
High Consumer's Experience.
It should be appreciated that respective field correspondence can also be directed in client tying in data structure or the first data
Metadata in structure and field name are processed accordingly, and to realize controlling database, one or more fields of table correspond to respectively
Metadata and field name whether shown in client.
Each embodiment of the present invention at least has the advantages that：
1st, in one embodiment of the invention, store at least one metadata by building database table in data base, with
When build to should database table the field annotation information to store this database table for the field annotation table, field information includes counting
According to each field corresponding code table respectively of storehouse table, in code table, have recorded at least one rendering parameter and at least one metadata
Between mapping relations；Accordingly, by building the field annotation table of correspondence database table in data base, with data storage storehouse
Mapping relations between metadata and rendering parameter under each field of table, store under client needs to database table when existing
Metadata when being rendered and showing, then can obtain the mapping between respective meta-data and rendering parameter according to field annotation table
Relation, it is not necessary to frequent updating client, can improve Consumer's Experience.
2nd, in one embodiment of the invention, by different code tables come identical unit under the different field of database of record table respectively
The data mapping relations between different rendering parameter respectively, can enable the client to accurately be directed to using different rendering parameter
Under different field in database table, identical metadata is rendered respectively and is shown.
3rd, in one embodiment of the invention, field annotation table storage field annotation information also include database table each
Field name respectively corresponding rendering parameter, can make client pass through to parse field annotation information determine database table each
Field name corresponding rendering parameter respectively, and then using corresponding field name in corresponding rendering parameter replacement data structure, realize
The field name of database table is rendered and is shown.
4th, in one embodiment of the invention, by building Major key table in data base with each word of data storage storehouse table
Section corresponding Major key (digest value of such as each field name) respectively, client is getting each word of database table
Section is respectively after corresponding Major key, you can using corresponding operation strategy, according to corresponding Major key, database table is specified
The corresponding code table of field is updated, and such as increases newly, in code table at least one rendering parameter and at least one unit are deleted or modified
The mapping relations of data, and then update corresponding data structure using amended code table, thus realizing needing with reference to practical business
Ask, carry out User Defined for the metadata display rule under the respective field of database table and render and show.
It should be noted that herein, such as first and second etc relational terms are used merely to an entity
Or operation is made a distinction with another entity or operation, and not necessarily requires or imply exist between these entities or operation
Any this actual relation or order.And, term " inclusion ", "comprising" or its any other variant are intended to non-
The comprising of exclusiveness, so that including a series of process of key elements, method, article or equipment not only include those key elements,
But also include other key elements being not expressly set out, or also include being consolidated by this process, method, article or equipment
Some key elements.In the absence of more restrictions, the key element being limited by sentence " including ", does not arrange
Remove and also there is other same factor in the process including described key element, method, article or equipment.
Last it should be noted that：The foregoing is only presently preferred embodiments of the present invention, be merely to illustrate the skill of the present invention
Art scheme, is not intended to limit protection scope of the present invention.All any modifications made within the spirit and principles in the present invention,
Equivalent, improvement etc., are all contained in protection scope of the present invention.
Claims (10)
1. a kind of date storage method is it is characterised in that include：
Build database table in data base, the corresponding identification information of described database table is set；Build corresponding described data base
The field annotation table of table；Also include：
Store at least one metadata using described database table；
Store the field annotation information of described database table using described field annotation table；Wherein, described field annotation information bag
Include each field respectively corresponding code table of described database table, described code table record have at least one rendering parameter with least
Mapping relations between one metadata.
2. date storage method according to claim 1 is it is characterised in that also include：
Build the form annotation table of corresponding described database table；Store the form of described database table using described form annotation table
Annotation information；Wherein, the designated separators of described form annotation information become at least two chunk；
And/or,
Build the Major key table of corresponding described database table；Store each word of described database table using described Major key table
Section corresponding Major key respectively.
3. date storage method according to claim 1 and 2 it is characterised in that
When storing the field annotation information of described database table using described field annotation table, if in same described code table
Record has the mapping relations between at least two rendering parameter and at least two metadata, then each using specified separators
Individual described metadata corresponding mapping relations respectively.
4. a kind of data base is it is characterised in that include：
Database table, and the field annotation table of corresponding described database table；Wherein,
Described database table, for storing at least one metadata；
Described field annotation table, for storing the field annotation information of described database table；Wherein, described field annotation information bag
Include each field respectively corresponding code table of described database table, described code table record have at least one rendering parameter with least
Mapping relations between one metadata.
5. data base according to claim 4 it is characterised in that
Also include：The form annotation table of corresponding described database table, and/or, the Major key table of corresponding described database table；Its
In,
Described form annotation table, for storing the form annotation information of described database table；Wherein, described form annotation information quilt
Specified separators become at least two chunk；
Described Major key table, for storing each field corresponding Major key respectively of described database table.
6. a kind of data managing method is it is characterised in that be applied in client, including：
Obtain the identification information of target database table, the data acquisition carrying described identification information to service middleware transmission please
Ask；
Receive the data structure of described target database table and the word that service middleware obtains according to described identification information and forwards
Section annotation information；
Parse described field annotation information to obtain each field corresponding code table respectively of described target database table, its
In, described code table record has the mapping relations between at least one rendering parameter and at least one metadata；
According to the mapping relations recording respectively in each described code table, replace described number using at least one rendering parameter described
According to metadata corresponding in structure to form first object data structure；
Form and show the first displaying form of corresponding described database table according to described first object data structure.
7. data managing method according to claim 6 it is characterised in that
The described data structure receiving the described target database table that service middleware obtains according to described identification information and forwards
And field annotation information, further include：Receive the described target that service middleware obtains according to described identification information and forwards
The form annotation information of database table；Described parse described field annotation information with obtain described target database table each
Field corresponding code table respectively, further includes：Parse described form annotation information, to determine quilt in described form annotation information
At least two chunk of specified separators；Described according to described first object data structure formed and show corresponding described in
First displaying form of target database table, further includes：Show each described information block；
And/or,
The described data structure receiving the described target database table that service middleware obtains according to described identification information and forwards
And field annotation information, further include：Receive the described target that service middleware obtains according to described identification information and forwards
Each field of database table corresponding Major key respectively；
In described the first displaying table being formed according to described first object data structure and showing corresponding described target database table
After lattice, also include：
Receive code table operational order, wherein, described code table operational order carries target Major key and operation strategy；
Determine the corresponding aiming field of described target Major key, and determine described aiming field corresponding target code table；
According to described operation strategy, the mapping relations of record in described target code table are processed accordingly；
According to the mapping relations of record in the described target code table after processing, update corresponding institute in described first object data structure
The target metadata stating aiming field is to form the second target data structure；
Form and show the second displaying form of corresponding described target database table according to described second target data structure.
8. a kind of client is it is characterised in that include：
Request of data unit, for obtaining the identification information of target database table, sends to service middleware and carries described mark
The data acquisition request of information；
Data receipt unit, for receiving the described target database that service middleware obtains according to described identification information and forwards
The data structure of table and field annotation information；
Data resolution unit, each field for parsing described field annotation information to obtain described target database table is divided
Not corresponding code table, wherein, described code table record has the mapping between at least one rendering parameter and at least one metadata to close
System；
Data mapping unit, for according to the mapping relations recording respectively in each described code table, using described at least one
In the rendering parameter described data structure of replacement, corresponding metadata is to form first object data structure；
Display processing unit, for forming according to described first object data structure and showing the first of corresponding described database table
Show form.
9. client according to claim 8 it is characterised in that
Described data receipt unit, is further used for receiving service middleware and is obtained and described in forwarding according to described identification information
The form annotation information of target database table；
Described data resolution unit, is further used for parsing described form annotation information, to determine in described form annotation information
At least two chunk of designated separators；
Described display processing unit, is further used for showing each described information block；
And/or,
Also include：Instruction reception unit, determining unit, code table processing unit；Wherein,
Described data receipt unit, is further used for receiving service middleware and is obtained and described in forwarding according to described identification information
Each field of target database table corresponding Major key respectively；
Described instruction reception unit, for receiving code table operational order, wherein, described code table operational order carries target Major key
And operation strategy；
Described determining unit, for determining the corresponding aiming field of described target Major key, and determines described aiming field pair
The target code table answered；
Described code table processing unit, for carrying out phase according to described operation strategy to the mapping relations of record in described target code table
The process answered；
Described data mapping unit, is further used for the mapping relations according to record in the described target code table after processing, updates
In described first object data structure, the target metadata of corresponding described aiming field is to form the second target data structure；
Described display processing unit, is further used for forming and show corresponding described target according to described second target data structure
Second displaying form of database table.
10. a kind of data management system is it is characterised in that include：
Service middleware, the data base as described in the claims 4 or 5, and as described in the claims 8 or 9
Client；Wherein,
Described service middleware, the data for receiving the identification information carrying target database table that described client sends obtains
Take request；The data structure of target database table and corresponding described target in described data base are obtained according to described identification information
The field annotation information of database table, and it is forwarded to described client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610841153.8A CN106407404B (en) | 2016-09-22 | 2016-09-22 | Date storage method, data managing method and system, database, client |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610841153.8A CN106407404B (en) | 2016-09-22 | 2016-09-22 | Date storage method, data managing method and system, database, client |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106407404A true CN106407404A (en) | 2017-02-15 |
| CN106407404B CN106407404B (en) | 2019-09-24 |
Family
ID=57996897
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610841153.8A Expired - Fee Related CN106407404B (en) | 2016-09-22 | 2016-09-22 | Date storage method, data managing method and system, database, client |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106407404B (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108241499A (en) * | 2018-01-05 | 2018-07-03 | 金行家（深圳）文化传播有限公司 | Update method, device and the computer readable storage medium of field value annotation |
| CN108776587A (en) * | 2018-05-25 | 2018-11-09 | 平安科技（深圳）有限公司 | Data capture method, device, computer equipment and storage medium |
| CN109254971A (en) * | 2018-08-31 | 2019-01-22 | 新华三大数据技术有限公司 | Resource inventory method and device |
| CN109271392A (en) * | 2018-10-30 | 2019-01-25 | 长威信息科技发展股份有限公司 | Quick discrimination and the method and apparatus for extracting relevant database entity and attribute |
| CN109669995A (en) * | 2018-12-25 | 2019-04-23 | 北京锐安科技有限公司 | Data storage, quality calculation method, device, storage medium and server |
| CN110297813A (en) * | 2019-05-22 | 2019-10-01 | 平安银行股份有限公司 | Data migration method, device, computer equipment and storage medium |
| CN110633331A (en) * | 2019-09-12 | 2019-12-31 | 金蝶蝶金云计算有限公司 | Method, system and related equipment for extracting data in relational database |
| CN110647452A (en) * | 2019-08-30 | 2020-01-03 | 深圳壹账通智能科技有限公司 | Test method, test device, computer equipment and storage medium |
| CN111078671A (en) * | 2019-12-19 | 2020-04-28 | 北京启迪区块链科技发展有限公司 | Method, device, equipment and medium for modifying data table field |
| CN111259013A (en) * | 2020-02-03 | 2020-06-09 | 京东数字科技控股有限公司 | Method and device for storing data |
| CN111339463A (en) * | 2020-02-19 | 2020-06-26 | 望海康信(北京)科技股份公司 | List data display method and device and electronic equipment |
| CN112860955A (en) * | 2021-03-01 | 2021-05-28 | 杨皓淳 | Business data management system and method based on cloud computing and big data |
| CN114595291A (en) * | 2022-05-10 | 2022-06-07 | 城云科技（中国）有限公司 | Collection task adjusting method and device based on database annotation |
| CN115037610A (en) * | 2022-04-24 | 2022-09-09 | 浙江清捷智能科技有限公司 | Automatic configuration system and automatic configuration method |
| CN115376636A (en) * | 2022-08-05 | 2022-11-22 | 河南翔宇医疗设备股份有限公司 | Method, system and device for generating gauge and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030084028A1 (en) * | 2001-10-31 | 2003-05-01 | Inventec Corporation | Method for storing records in database or reading the same therefrom |
| CN201689418U (en) * | 2010-04-14 | 2010-12-29 | 北京喻龙恒瑞科技有限公司 | Management data sheet updating device and managing system |
| CN103440272A (en) * | 2013-08-05 | 2013-12-11 | 北京康邦科技有限公司 | Database maintenance method and device |
-
2016
- 2016-09-22 CN CN201610841153.8A patent/CN106407404B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030084028A1 (en) * | 2001-10-31 | 2003-05-01 | Inventec Corporation | Method for storing records in database or reading the same therefrom |
| CN201689418U (en) * | 2010-04-14 | 2010-12-29 | 北京喻龙恒瑞科技有限公司 | Management data sheet updating device and managing system |
| CN103440272A (en) * | 2013-08-05 | 2013-12-11 | 北京康邦科技有限公司 | Database maintenance method and device |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108241499A (en) * | 2018-01-05 | 2018-07-03 | 金行家（深圳）文化传播有限公司 | Update method, device and the computer readable storage medium of field value annotation |
| CN108776587B (en) * | 2018-05-25 | 2020-07-17 | 平安科技（深圳）有限公司 | Data acquisition method and device, computer equipment and storage medium |
| CN108776587A (en) * | 2018-05-25 | 2018-11-09 | 平安科技（深圳）有限公司 | Data capture method, device, computer equipment and storage medium |
| CN109254971A (en) * | 2018-08-31 | 2019-01-22 | 新华三大数据技术有限公司 | Resource inventory method and device |
| CN109271392A (en) * | 2018-10-30 | 2019-01-25 | 长威信息科技发展股份有限公司 | Quick discrimination and the method and apparatus for extracting relevant database entity and attribute |
| CN109271392B (en) * | 2018-10-30 | 2022-07-26 | 长威信息科技发展股份有限公司 | Method and equipment for quickly distinguishing and extracting relational database entity and attribute |
| CN109669995A (en) * | 2018-12-25 | 2019-04-23 | 北京锐安科技有限公司 | Data storage, quality calculation method, device, storage medium and server |
| CN110297813A (en) * | 2019-05-22 | 2019-10-01 | 平安银行股份有限公司 | Data migration method, device, computer equipment and storage medium |
| CN110647452B (en) * | 2019-08-30 | 2023-02-07 | 深圳壹账通智能科技有限公司 | Test method, test device, computer equipment and storage medium |
| CN110647452A (en) * | 2019-08-30 | 2020-01-03 | 深圳壹账通智能科技有限公司 | Test method, test device, computer equipment and storage medium |
| CN110633331A (en) * | 2019-09-12 | 2019-12-31 | 金蝶蝶金云计算有限公司 | Method, system and related equipment for extracting data in relational database |
| CN110633331B (en) * | 2019-09-12 | 2022-08-23 | 金蝶蝶金云计算有限公司 | Method, system and related equipment for extracting data in relational database |
| CN111078671A (en) * | 2019-12-19 | 2020-04-28 | 北京启迪区块链科技发展有限公司 | Method, device, equipment and medium for modifying data table field |
| CN111259013A (en) * | 2020-02-03 | 2020-06-09 | 京东数字科技控股有限公司 | Method and device for storing data |
| CN111339463A (en) * | 2020-02-19 | 2020-06-26 | 望海康信(北京)科技股份公司 | List data display method and device and electronic equipment |
| CN111339463B (en) * | 2020-02-19 | 2023-07-04 | 望海康信(北京)科技股份公司 | Display method and device of list data and electronic equipment |
| CN112860955A (en) * | 2021-03-01 | 2021-05-28 | 杨皓淳 | Business data management system and method based on cloud computing and big data |
| CN112860955B (en) * | 2021-03-01 | 2022-03-08 | 杨皓淳 | Business data management system and method based on cloud computing and big data |
| CN115037610A (en) * | 2022-04-24 | 2022-09-09 | 浙江清捷智能科技有限公司 | Automatic configuration system and automatic configuration method |
| CN115037610B (en) * | 2022-04-24 | 2023-09-22 | 浙江清捷智能科技有限公司 | Automatic configuration system and automatic configuration method |
| CN114595291A (en) * | 2022-05-10 | 2022-06-07 | 城云科技（中国）有限公司 | Collection task adjusting method and device based on database annotation |
| CN115376636A (en) * | 2022-08-05 | 2022-11-22 | 河南翔宇医疗设备股份有限公司 | Method, system and device for generating gauge and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106407404B (en) | 2019-09-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106407404A (en) | A data storage method, a data management method and system, a database and a client | |
| CN101512570B (en) | For the method and system of portable data aggregation | |
| CN107341206B (en) | The method for constructing accurately user's portrait system based on multiple data sources | |
| CN102982097B (en) | Domain for Knowledge based engineering data quality solution | |
| CN109299100B (en) | Managing internal memory data and the method and system for safeguarding data in memory | |
| CN105373541B (en) | The processing method and system of the data operation request of database | |
| CN105338113B (en) | A kind of multi-platform data interconnection system for Urban Data resource-sharing | |
| CN108228817A (en) | Data processing method, device and system | |
| CN105518658A (en) | Apparatus, systems, and methods for grouping data records | |
| US20150127599A1 (en) | Stateless database cache | |
| CN105849726A (en) | Generic indexing for efficiently supporting ad-hoc query over hierarchically marked-up data | |
| US20090319559A1 (en) | Method And System of Using Social Networks and Communities to Ensure Data Quality of Configuration Items in a Configuration Management Database | |
| CN108090165A (en) | A kind of acquisition methods of the collection of illustrative plates variation based on embedded chart database | |
| CN106503214A (en) | A kind of complex rule matching process based on Redis memory databases | |
| CN108038175A (en) | Multidimensional data dynamically associates querying method, device, computer equipment and medium | |
| CN107832392A (en) | A kind of metadata management system | |
| CN103744948B (en) | Searching data checks the method and system of reason of discrepancies | |
| US20080027899A1 (en) | Systems and Methods for Integrating from Data Sources to Data Target Locations | |
| CN112463986A (en) | Information storage method and device | |
| CN106817626B (en) | A kind of network direct broadcasting present is shown and construction method | |
| CN109359127A (en) | A kind of querying method of electronic invoice, device, equipment and storage medium | |
| CN112214609B (en) | Audit method and system based on knowledge graph | |
| CN107977865A (en) | Advertisement sending method, device, computer equipment and readable storage medium storing program for executing | |
| CN107357930A (en) | Cloud account mill platform tenant data table structure | |
| US10055110B2 (en) | Simulating a user interface to submit data received from a device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20190924 Termination date: 20200922 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |