CN103617168B - Universal metadata verifying and exporting method - Google Patents
Universal metadata verifying and exporting method Download PDFInfo
- Publication number
- CN103617168B CN103617168B CN201310500801.XA CN201310500801A CN103617168B CN 103617168 B CN103617168 B CN 103617168B CN 201310500801 A CN201310500801 A CN 201310500801A CN 103617168 B CN103617168 B CN 103617168B
- Authority
- CN
- China
- Prior art keywords
- metadata
- configuration file
- check
- tag
- configuration
- 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.)
- Expired - Fee Related
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/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- 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/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
Abstract
The invention discloses a universal metadata verifying and exporting method. A program establishes a plug-and-play type universal metadata exporting module, and the plug-and-play type universal metadata exporting module can be arranged in a decentralized self-discipline electric power data management platform in a hot plugging mode. The plug-and-play type universal metadata exporting module supports that any metadata which are stored in the electric power data management platform in a mode of three-layer HashMap mode are exported to a relational high-volume database in a customized mode. By the adoption of the universal metadata verifying and exporting method, the metadata in a Felix container (an internal memory) are stored into the relational database continuously, so that the metadata have the historical retrospection performance, and meanwhile the difficulty of achievement of the purpose that each downlink data query and analysis sub system can conveniently and flexibly obtain real-time or historical metadata is effectively reduced.
Description
Technical field
The present invention relates to electric power system data processing method field, specially a kind of general metadata verification and derivation side
Method.
Background technology
Scattered plug and play data platform of restraining oneself adopts to be tied using the metadata that three layers of HashMap form represent as unified
Structure is storing the electric power data of various forms.Though metadata solves the normalized problem of isomeric data, it is limited to internal memory and holds
The factors such as amount, it cannot meet the demand under production environment, mass historical data inquired about and analyzed.
Electric power applications numerous at present to store magnanimity historical production data using relevant database mostly, but they are each
From based on data standard and form often different, thus result in the difference of database table structure.Therefore, existing power system
As a consequence it is hardly possible to be multiplexed the creation data of other system, thus increased each data in downstream looking on the premise of not changing code
Ask the development difficulty with analyzing subsystem and cost.
Content of the invention
In order to overcome the above-mentioned deficiencies of the prior art, it is an object of the invention to provide a kind of general metadata verification and leading
Go out method.
In order to achieve the above object, the technical solution adopted in the present invention is:
A kind of general metadata verification and deriving method it is characterised in that:Program construction instant inserted and instant using type general
Metadata export module, described metadata export module logical structure is as follows:
Derive the definition of configuration, configuration information necessary to editing meta-data derivation, configuration information is saved in UI or configuration
In file;
Derive the verification of configuration, check whether the derivation configuration information in UI or configuration file is consistent with actual metadata;
The verification in data with existing storehouse, when selecting to export to already present data base, checks that metadata and derivation configuration are
The no structure with data with existing storehouse is consistent;
The lasting storage of meta-data snap, will turn to this with the metadata sequence that three layers of HashMap form are deposited in internal memory
Ground file;
The manual method of operation, the UI that user is provided by operation module derives configuration information and executes Lai self-defined and verification
Derive;
Automatic running mode, in the realization scattered plug and play electric power data management platform of self-discipline, output layer definition connects
Mouthful, and the verification and the derivation that complete metadata containing the configuration file deriving configuration information manually obtaining under the method for operation
Logic.
Described a kind of general metadata verification and deriving method it is characterised in that:The described definition bag deriving configuration
Include markers definition, Tag/Key definition, the definition procedure deriving configuration is as follows:
Step 1:Manual mode starting module, selects metadata to be derived;
Step 2:For each Tag in metadata, select or whether editor derives this Tag, this Tag correspondence database table
Title, which Key deriving under this Tag, each Key corresponding Database field title and type, whether contain markers, when
Mark corresponding Tag/Key.
Described a kind of general metadata verification and deriving method it is characterised in that:The described verification bag deriving configuration
Include metadata verification, time scale check, there is data base's verification, the checking procedure deriving configuration is as follows:
Step 1:Whether inspection metadata to be derived does not comprise any Tag;
Step 2:Check whether configuration file does not comprise any Tag;
Step 3:Check whether configuration file contains the Tag of entitled sky;
Step 4:Check whether one or more Tag of the metadata to be derived that configuration file is specified do not appear in configuration
In file;
Step 5:Check whether configuration file lacks metadata the to be derived whether information containing time labelling or this letter
Whether breath is illegal;
Step 6:Check whether configuration file lacks time labelling corresponding Tag/Key title, or whether this Tag/Key deposits
It is in metadata;
Step 7:Check whether configuration file lacks markers corresponding date and time form;
Step 8:Check that whether not specified the configuration file information whether deriving certain Tag/Key or this information is illegal;
Step 9:Check that whether not specified the corresponding table name of configuration file certain Tag or table name be illegal;
Step 10:Check that whether not specified the corresponding field name of configuration file certain Key or field name be illegal;
Step 11:Check that whether not specified the corresponding field type of configuration file certain Key or field type be illegal;
Step 12:Check multiple Tag corresponding table name identical situation that whether there is in configuration file;
Step 13:Check in configuration file with the presence or absence of the multiple Key corresponding field name identical feelings under a certain Tag
Condition;
Step 14:Check all be appointed as not deriving with the presence or absence of all Tag in configuration file or a certain Tag under own
Key is appointed as situation about not deriving.
Described a kind of general metadata verification and deriving method it is characterised in that:The verification in described data with existing storehouse
Based on metadata to be derived, the table in data with existing storehouse, field and field type are checked, the verification in data with existing storehouse
Journey is as follows:
Step 1:Check that deriving the existing storehouse specified in configuration whether there is;
Step 2:Check to derive to whether there is in configuration and " carried out to the data base being created by Third party system with historical manner
The situation of derivation ";
Step 3:Check that the table name that configuration file is specified whether there is in specified existing storehouse;
Step 4:Check that the field name that configuration file is specified whether there is in specified existing storehouse;
Step 5:Check the field type specified of configuration file whether with specified existing storehouse in respective field type
Unanimously;
Step 6:Check the field type specified of configuration file whether with specified existing storehouse in respective field type
Unanimously.
Described a kind of general metadata verification and deriving method it is characterised in that:Will be arbitrarily with three layers of HashMap shape
The metadata that formula is deposited snapshot at a time is persisted in local file in the way of object serialization, and when needed
To its unserializing to obtain the snapshot of metadata.
Described a kind of general metadata verification and deriving method it is characterised in that:Restrain oneself scattered plug and play number
According to platform can manually obtain under the method for operation containing the configuration file deriving configuration information, be automatically performed metadata
Verification and derivation logic, process is as follows:
Step 1:Run this module in a manual manner;
Step 2:The UI of user operation module, selects and editor derives configuration information, and configuration information is saved as configuration
File;
Step 3:Start scattered plug and play data platform of restraining oneself, and in data platform in the way of visualizing towing
Output layer creates the example of this module;
Step 4:For example specified configuration file, and start example, hereafter data platform will be by output layer interface definition
Callback method trigger metadata verification and derive logic.
The metadata in scattered plug and play data platform of restraining oneself is persistently stored in by the present invention in definable mode
So that metadata possesses history can recall feature in relevant database, also effectively reduce simultaneously each data query in downstream and
Analyzing subsystem easily and flexibly obtains real-time or history metadata difficulty.
The present invention compared with prior art, has the advantage that:
(1), module plug and play, definable degree is high.Module is with the Bundle form hot plug of OSGi to data management
In platform, all can configure partly all is left in independent configuration file or is specified by the UI of data management platform.
(2), code is clearly layered, and extensibility is high.Module is divided into the logical layers such as Model, Dao, Biz and UI, layer
Between unidirectional dependence, the quick demand of power grid application is become and has more good adaptability.
(3), support MySQL and oracle database simultaneously, multiple modules concurrently to write out efficiency higher.Wherein, MySQL
For the rapid deployment of module, test and demonstration;Oracle is used for actual production environment.Metadata is derived with historical manner
When, automatically set up table index by markers it is ensured that the search efficiency of mass data.
(4), perfect check logic and detailed information.Either manual still automatic running mode, module is equal
Provide various be likely to occur be not intended to or malice derive configuration check logic and detailed miscue information.
Brief description
Fig. 1 is function of the present invention and logical partitioning figure.
Fig. 2 is the preservation flow chart deriving configuration information under the manual method of operation of the present invention.
The flow chart that Fig. 3 exports to data base for metadata of the present invention.
Specific embodiment
A kind of general metadata verification and deriving method, the general metadata of program construction instant inserted and instant using type derives mould
Block, metadata export module logical structure is as follows:
Derive the definition of configuration, configuration information necessary to editing meta-data derivation, configuration information is saved in UI or configuration
In file;
Derive the verification of configuration, check whether the derivation configuration information in UI or configuration file is consistent with actual metadata;
The verification in data with existing storehouse, when selecting to export to already present data base, checks that metadata and derivation configuration are
The no structure with data with existing storehouse is consistent;
The lasting storage of meta-data snap, will turn to this with the metadata sequence that three layers of HashMap form are deposited in internal memory
Ground file;
The manual method of operation, the UI that user is provided by operation module derives configuration information and executes Lai self-defined and verification
Derive;
Automatic running mode, in the realization scattered plug and play electric power data management platform of self-discipline, output layer definition connects
Mouthful, and the verification and the derivation that complete metadata containing the configuration file deriving configuration information manually obtaining under the method for operation
Logic.
The definition deriving configuration includes markers definition, Tag/Key definition, and the definition procedure deriving configuration is as follows:
Step 1:Manual mode starting module, selects metadata to be derived;
Step 2:For each Tag in metadata, select or whether editor derives this Tag, this Tag correspondence database table
Title, which Key deriving under this Tag, each Key corresponding Database field title and type, whether contain markers, when
Mark corresponding Tag/Key.
The verification deriving configuration includes metadata verification, time scale check, there is data base's verification, derives the verification of configuration
Process is as follows:
Step 1:Whether inspection metadata to be derived does not comprise any Tag;
Step 2:Check whether configuration file does not comprise any Tag;
Step 3:Check whether configuration file contains the Tag of entitled sky;
Step 4:Check whether one or more Tag of the metadata to be derived that configuration file is specified do not appear in configuration
In file;
Step 5:Check whether configuration file lacks metadata the to be derived whether information containing time labelling or this letter
Whether breath is illegal;
Step 6:Check whether configuration file lacks time labelling corresponding Tag/Key title, or whether this Tag/Key deposits
It is in metadata;
Step 7:Check whether configuration file lacks markers corresponding date and time form;
Step 8:Check that whether not specified the configuration file information whether deriving certain Tag/Key or this information is illegal;
Step 9:Check that whether not specified the corresponding table name of configuration file certain Tag or table name be illegal;
Step 10:Check that whether not specified the corresponding field name of configuration file certain Key or field name be illegal;
Step 11:Check that whether not specified the corresponding field type of configuration file certain Key or field type be illegal;
Step 12:Check multiple Tag corresponding table name identical situation that whether there is in configuration file;
Step 13:Check in configuration file with the presence or absence of the multiple Key corresponding field name identical feelings under a certain Tag
Condition;
Step 14:Check all be appointed as not deriving with the presence or absence of all Tag in configuration file or a certain Tag under own
Key is appointed as situation about not deriving.
The verification in data with existing storehouse, based on metadata to be derived, is entered to the table in data with existing storehouse, field and field type
Row checks, the checking procedure in data with existing storehouse is as follows:
Step 1:Check that deriving the existing storehouse specified in configuration whether there is;
Step 2:Check to derive to whether there is in configuration and " carried out to the data base being created by Third party system with historical manner
The situation of derivation ";
Step 3:Check that the table name that configuration file is specified whether there is in specified existing storehouse;
Step 4:Check that the field name that configuration file is specified whether there is in specified existing storehouse;
Step 5:Check the field type specified of configuration file whether with specified existing storehouse in respective field type
Unanimously;
Step 6:Check the field type specified of configuration file whether with specified existing storehouse in respective field type
Unanimously.
By arbitrarily in the way of metadata that three layers of HashMap form are deposited snapshot at a time is with object serialization
Persist in local file, and when needed to its unserializing to obtain the snapshot of metadata.
Scattered plug and play data platform of restraining oneself can manually obtain under the method for operation containing deriving configuration letter
The configuration file of breath, is automatically performed the verification of metadata and derives logic, process is as follows:
Step 1:Run this module in a manual manner;
Step 2:The UI of user operation module, selects and editor derives configuration information, and configuration information is saved as configuration
File;
Step 3:Start scattered plug and play data platform of restraining oneself, and in data platform in the way of visualizing towing
Output layer creates the example of this module;
Step 4:For example specified configuration file, and start example, hereafter data platform will be by output layer interface definition
Callback method trigger metadata verification and derive logic.
As shown in figure 1, the present invention passes through the general metadata export module of program construction, can plug and play restrain oneself to dispersion
In electric power data management platform.Module supports the output layer interface with manual operation UI with automatically by electric power data management platform
2 kinds of working methods of readjustment complete to derive the editor configuring, verification, the lasting storage of preservation, loading and metadata.
Embodiment 1, derives the preservation of configuration information under manual mode.
Under the manual method of operation, user can by UI editor various derivation configuration informations save as configuration file with
For being verified to metadata in an automatic fashion in data platform and deriving, idiographic flow is as shown in Figure 2.User puts down from data
Metadata to be derived is chosen, module dynamically will generate UI so that user selects and editor and markers, Tag/Key, table/word in platform
The derivation configuration information of Duan Youguan, and after editor finishes, all derivation configuration informations can be saved as property file.
Embodiment 2, metadata is exported to relevant database.
After data platform gets metadata, should according to Tag in the configuration file preserving before and metadata and
The mapping relations of Key, the structure of dynamic creation data base and each table, and metadata is exported in respective table, idiographic flow is such as
Shown in Fig. 3.
Fig. 3 contains several extra flow processs.When executing derivation first, should create Root storehouse derives history confession to record
Downstream module is inquired about;Check that 1 refers to the UI to manual mode or the check logic of configuration file execution that automated manner is specified;Inspection
Look into 2 to refer to need the check logic of execution when exporting to the data base of already present particularly third-party application system creation;
Check 3 check logic referring to the mapping relations of Tag/ table each in configuration file, Key/ field are carried out.
Claims (6)
1. a kind of general metadata verification and deriving method it is characterised in that:The general unit of program construction instant inserted and instant using type
Data export module, described metadata export module logic flow is as follows:
Derive the definition of configuration, configuration information necessary to editing meta-data derivation, configuration information is saved in UI or configuration file
In;
Derive the verification of configuration, check whether the derivation configuration information in UI or configuration file is consistent with actual metadata;
The verification in data with existing storehouse, selects when exporting to already present data base, check metadata and derive configuration whether with
The structure in data with existing storehouse is consistent;
The lasting storage of meta-data snap, will turn to local literary composition with the metadata sequence that three layers of HashMap form are deposited in internal memory
Part;
Manual operational process, the UI that user is provided by operation module derives configuration information executing Lai self-defined and verification and leads
Go out;
Automatic running flow process, realizes the interface of output layer definition in the scattered plug and play electric power data management platform of self-discipline, and
Manually obtain under operational process completes the verification of metadata containing the configuration file deriving configuration information and derives logic.
2. a kind of general metadata verification according to claim 1 and deriving method it is characterised in that:Described derivation is joined
The definition put includes markers definition, Tag/Key definition, and the definition procedure deriving configuration is as follows:
Step 1:Manual mode starting module, selects metadata to be derived;
Step 2:For each Tag in metadata, select or whether editor derives this Tag, the name of this Tag correspondence database table
Title, which Key deriving under this Tag, each Key corresponding Database field title and type, whether contain markers, markers pair
The Tag/Key answering.
3. a kind of general metadata verification according to claim 1 and deriving method it is characterised in that:Described derivation is joined
The verification put includes metadata verification, time scale check, there is data base's verification, and the checking procedure deriving configuration is as follows:
Step 1:Whether inspection metadata to be derived does not comprise any Tag;
Step 2:Check whether configuration file does not comprise any Tag;
Step 3:Check whether configuration file contains the Tag of entitled sky;
Step 4:Check whether one or more Tag of the metadata to be derived that configuration file is specified do not appear in configuration file
In;
Step 5:Check whether lack metadata to be derived by configuration file whether the information containing time labelling or this information are
No illegal;
Step 6:Check configuration file whether lack time labelling corresponding Tag/Key title, or this Tag/Key whether there is in
In metadata;
Step 7:Check whether configuration file lacks markers corresponding date and time form;
Step 8:Check that whether not specified the configuration file information whether deriving certain Tag/Key or this information is illegal;
Step 9:Check that whether not specified the corresponding table name of configuration file certain Tag or table name be illegal;
Step 10:Check that whether not specified the corresponding field name of configuration file certain Key or field name be illegal;
Step 11:Check that whether not specified the corresponding field type of configuration file certain Key or field type be illegal;
Step 12:Check multiple Tag corresponding table name identical situation that whether there is in configuration file;
Step 13:Check in configuration file with the presence or absence of the multiple Key corresponding field name identical situation under a certain Tag;
Step 14:Check all be appointed as not deriving with the presence or absence of all Tag in configuration file or a certain Tag under all Key all
It is appointed as situation about not deriving.
4. a kind of general metadata verification according to claim 1 and deriving method it is characterised in that:Described count
Verifying based on metadata to be derived according to storehouse, checks to the table in data with existing storehouse, field and field type, data with existing
The checking procedure in storehouse is as follows:
Step 1:Check that deriving the existing storehouse specified in configuration whether there is;
Step 2:Check to derive to whether there is in configuration and " led to the data base being created by Third party system with historical manner
Go out " situation;
Step 3:Check that the table name that configuration file is specified whether there is in specified existing storehouse;
Step 4:Check that the field name that configuration file is specified whether there is in specified existing storehouse;
Step 5:Check whether the field type that configuration file is specified is consistent with the type of the respective field in specified existing storehouse;
Step 6:Check whether the field type that configuration file is specified is consistent with the type of the respective field in specified existing storehouse.
5. a kind of general metadata verification according to claim 1 and deriving method it is characterised in that:Will be arbitrarily with three
The metadata that layer HashMap form is deposited snapshot at a time is persisted in locally literary composition in the way of object serialization
Part, and when needed to its unserializing to obtain the snapshot of metadata.
6. a kind of general metadata verification according to claim 1 and deriving method it is characterised in that:Self-discipline is scattered
Plug and play data platform manually obtain under operational process containing the configuration file deriving configuration information, be automatically performed unit
The verification of data and derivation logic, process is as follows:
Step 1:Run this module in a manual manner;
Step 2:The UI of user operation module, selects and editor derives configuration information, and configuration information is saved as configuration file;
Step 3:Start scattered plug and play data platform of restraining oneself, and in the output of data platform in the way of visualizing towing
Layer creates the example of this module;
Step 4:For example specified configuration file, and start example, hereafter data platform is by returning by output layer interface definition
Tune method triggers the verification of metadata and derives logic.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310500801.XA CN103617168B (en) | 2013-10-22 | 2013-10-22 | Universal metadata verifying and exporting method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310500801.XA CN103617168B (en) | 2013-10-22 | 2013-10-22 | Universal metadata verifying and exporting method |
Publications (2)
Publication Number | Publication Date |
---|---|
CN103617168A CN103617168A (en) | 2014-03-05 |
CN103617168B true CN103617168B (en) | 2017-02-15 |
Family
ID=50167871
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201310500801.XA Expired - Fee Related CN103617168B (en) | 2013-10-22 | 2013-10-22 | Universal metadata verifying and exporting method |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN103617168B (en) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107330031B (en) * | 2017-06-26 | 2020-07-07 | 广州华多网络科技有限公司 | Data storage method and device and electronic equipment |
CN109063146A (en) * | 2018-08-07 | 2018-12-21 | 北京神州泰岳软件股份有限公司 | A kind of data export method, apparatus and system |
CN109344129A (en) * | 2018-08-16 | 2019-02-15 | 浙江众合科技股份有限公司 | A kind of signal system configuration file generation system and method for high reliability |
CN109408502A (en) * | 2018-11-14 | 2019-03-01 | 成都四方伟业软件股份有限公司 | A kind of data standard processing method, device and its storage medium |
CN109739831A (en) * | 2018-11-23 | 2019-05-10 | 网联清算有限公司 | Data verification method and device between database |
CN109597763B (en) * | 2018-12-04 | 2022-02-25 | 北京广利核系统工程有限公司 | Consistency verification method and device for normalizing multiple items of data |
CN112463857B (en) * | 2020-03-27 | 2023-07-25 | 谭凌 | Data processing method and system for supporting backtracking data query based on relational database |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7346627B2 (en) * | 2003-06-25 | 2008-03-18 | Oracle International Corporation | Approaches for migrating portal objects from a source installation to a target installation |
US20070083543A1 (en) * | 2005-10-07 | 2007-04-12 | Epiphany, Inc. | XML schema template builder |
CN101625694A (en) * | 2009-08-17 | 2010-01-13 | 中国科学院地理科学与资源研究所 | Method and system for storing various standard geological metadata |
US20110191304A1 (en) * | 2010-01-29 | 2011-08-04 | Software Ag, Inc. | System and method for export and import of metadata located in metadata registries |
CN101794225A (en) * | 2010-02-26 | 2010-08-04 | 南京师范大学 | GML analytic method based on GDOM and persistence thereof |
CN102682027A (en) * | 2011-03-16 | 2012-09-19 | 新奥特(北京)视频技术有限公司 | Method and system for importing and exporting Eclipse rich client platform (RCP) data |
US20130117326A1 (en) * | 2011-11-08 | 2013-05-09 | Microsoft Corporation | External serialization and deserialization |
CN103034928B (en) * | 2012-12-11 | 2015-11-18 | 清华大学 | The plug and play data platform of self-discipline dispersion and management method and application |
CN103150517B (en) * | 2013-02-06 | 2016-01-20 | 杭州电子科技大学 | Concerning security matters e-file stores archive method, user right and opening of documents permission match method of calibration |
-
2013
- 2013-10-22 CN CN201310500801.XA patent/CN103617168B/en not_active Expired - Fee Related
Also Published As
Publication number | Publication date |
---|---|
CN103617168A (en) | 2014-03-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN103617168B (en) | Universal metadata verifying and exporting method | |
CN103605663B (en) | General database checking and metadata loading method | |
CN103336805B (en) | A kind of report customization automatic generation method based on graphical mapping relations and device | |
CN104809247B (en) | The distribution of database connection and recovery method | |
CN109508355A (en) | A kind of data pick-up method, system and terminal device | |
CN107741903A (en) | Application compatibility method of testing, device, computer equipment and storage medium | |
CN109446104A (en) | A kind of testing case management and device based on big data | |
CN102043719A (en) | Method for testing IEC61850 configuration description file | |
CN103294805B (en) | The creation method of data warehouse personalization dimension table and device | |
CN102750301A (en) | Blueprint generating method for integrated avionic system model aiming at architecture analysis and design language (AADL) description | |
CN107659455A (en) | A kind of method, storage medium, equipment and the system of iOS ends Mock data | |
CN105608142A (en) | Storage method and device of Json data | |
CN109885474A (en) | Test case edit methods and device, terminal and computer readable storage medium | |
CN106021718A (en) | Drawing method and device used for engineering drawing in CATIA (Computer-graphics Aided Three-dimensional Interactive Application) | |
CN105512188A (en) | Data connection method and data connection system | |
CN110069376A (en) | Several method, apparatus, storage medium and computer equipment are made in a kind of association | |
CN109299205A (en) | The method and apparatus that will plan that the spatial data that industry uses is put in storage | |
US20180239791A1 (en) | Bitmap-based storage space management system and methods thereof | |
CN105373636A (en) | Enterprise Windchill system based ProE standard part library construction method | |
CN103258047B (en) | A kind of data organization method towards medicine enterprise Activity-Based Cost Control data warehouse | |
CN103150281B (en) | The integrated approach of bus bar module, device and verification method and device | |
CN102999663B (en) | Method for verifying MMU (Memory Management Unit) in SOC (System On Chip) | |
CN110347976A (en) | Method, system, device and the storage medium of quick equipment leading out data model | |
CN104021002A (en) | Method for storing PDM system standard components | |
CN103441988B (en) | Across GIS platform data migration method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C14 | Grant of patent or utility model | ||
GR01 | Patent grant | ||
CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20170215 Termination date: 20171022 |
|
CF01 | Termination of patent right due to non-payment of annual fee |