CN102110111A - Method and system for processing database operating command - Google Patents
Method and system for processing database operating command Download PDFInfo
- Publication number
- CN102110111A CN102110111A CN2009102442072A CN200910244207A CN102110111A CN 102110111 A CN102110111 A CN 102110111A CN 2009102442072 A CN2009102442072 A CN 2009102442072A CN 200910244207 A CN200910244207 A CN 200910244207A CN 102110111 A CN102110111 A CN 102110111A
- Authority
- CN
- China
- Prior art keywords
- order
- database manipulation
- database
- entityclass
- manipulation order
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 74
- 230000008569 process Effects 0.000 claims abstract description 30
- 238000005538 encapsulation Methods 0.000 claims description 20
- 238000012217 deletion Methods 0.000 claims description 13
- 230000037430 deletion Effects 0.000 claims description 13
- 230000009471 action Effects 0.000 claims description 6
- 238000003780 insertion Methods 0.000 claims description 3
- 230000037431 insertion Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 6
- 238000004364 calculation method Methods 0.000 description 5
- 230000008859 change Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012856 packing Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000001965 increasing effect Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 230000035807 sensation Effects 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for processing a database operating command, wherein the method comprises steps as follows: encapsulating the database operating command; and calling the encapsulated database operating command. The invention can simply and conveniently process the database operating command.
Description
Technical field
The present invention relates to field of computer technology, in particular to a kind of database manipulation process of commands method and device.
Background technology
The present invention relates to the encapsulation of database data process of commands method,, guarantee the reusability of data Layer operation for the developer provides a kind of method of general database manipulation, unitarity, thus the system of assurance is stable.
In the middle of the process of project exploitation, the exploitation member's of project team coding style difference and the dirigibility of data base manipulation statement SQL have brought increasing operation and maintenance difficulty to project team.Such as: take out all data from the user table, the somebody can be write as select*fromuser; The somebody can be write as select all from user; The somebody can write Select Name (all fields) from user.
Though do not have any mistake in operation, but when the process of other people reader, will produce bad sensation, can produce redundant code simultaneously, if the order of magnitude of this program difference in project is a lot, various styles will appear in program in the middle of the process of exploitation so, and the difficulty of maintenance increases greatly.
At present, be Hibernate for the widest of database manipulation encapsulation usefulness, relative merits are as follows.Advantage comprises: abandoned the thought of database hub, object-oriented thought does not need database knowledge completely, and it is low that the program member goes into gate threshold; Shortcoming comprises: heavy in hand under a large amount of multilists, complex query, need very deep grounding in basic skills; Debug difficulties is not easy left-hand seat; The relatively more tired lock of mapping complex, the integration environment.
At in the correlation technique to the problem of the operation more complicated of database, effective solution is not proposed at present as yet.
Summary of the invention
At in the correlation technique to the problem of the operation more complicated of database and propose the present invention, for this reason, fundamental purpose of the present invention is to provide a kind of database manipulation process of commands method and device, to address the above problem.
To achieve these goals, according to an aspect of the present invention, provide a kind of database manipulation process of commands method.
Database manipulation process of commands method according to the present invention comprises: the database operational order is encapsulated; Database manipulation order after the encapsulation is called.
Preferably, before the database operational order was encapsulated, method also comprised: receive the database manipulation order.
Preferably, the database manipulation order comprises one of following kind: insert operational order, retouching operation order, deletion action order, query manipulation order.
Preferably, under the situation of database manipulation order for insertion one of operational order, retouching operation order and deletion action order, method also comprises: judge whether to exist unusual when carrying out the database operational order; Exist under the unusual situation, then carrying out data rewind; Not existing under the unusual situation, then submit data to.
Preferably, after submitting data to, method also comprises: return the execution result that the database manipulation order after the encapsulation is called.
Preferably, be that method also comprises under the situation of query manipulation order in the database manipulation order: when carrying out the database operational order, judge whether to exist unusual; Do not exist under the unusual situation, then returning the result who carries out the query manipulation order.
Preferably, the database manipulation order after the encapsulation is called and comprised: the entity class of creating database.
Preferably, the database manipulation order after the encapsulation is called and comprised the following condition that is provided for calling: call the table name of database manipulation order, field and the operation species that needs are operated.
To achieve these goals, according to a further aspect in the invention, provide a kind of database manipulation process of commands device.
Database manipulation process of commands device according to the present invention comprises: package module encapsulates the database operational order; Calling module is used for the database manipulation order after the encapsulation is called.
Preferably, treating apparatus also comprises: judge module is used for judging when carrying out the database operational order whether exist unusually.
By the present invention, adopt the database operational order is encapsulated; Database manipulation order after the encapsulation is called, solved problem, and then reached the effect that realizes easily the operation of database the operation more complicated of database.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the process flow diagram according to the database manipulation process of commands method of the embodiment of the invention;
Fig. 2 is the process flow diagram according to the preferred database manipulation process of commands of embodiment of the invention method;
Fig. 3 is the database manipulation process of commands schematic representation of apparatus according to the embodiment of the invention.
Embodiment
Need to prove that under the situation of not conflicting, embodiment and the feature among the embodiment among the application can make up mutually.Describe the present invention below with reference to the accompanying drawings and in conjunction with the embodiments in detail.
According to embodiments of the invention, a kind of database manipulation process of commands method and device are provided.
Fig. 1 is the process flow diagram according to the database manipulation process of commands method of the embodiment of the invention.
As shown in Figure 1, this method comprises that following step S202 is to step S204:
Step S102 encapsulates the database operational order;
Step S104 calls the database manipulation order after the encapsulation.
Preferably, before the database operational order was encapsulated, this method also comprised: receive the database manipulation order.
Preferably, the database manipulation order comprises one of following kind: insert operational order, retouching operation order, deletion action order, query manipulation order.
Preferably, under the situation of database manipulation order for insertion one of operational order, retouching operation order and deletion action order, this method also comprises: judge whether to exist unusual when carrying out the database operational order; Exist under the unusual situation, then carrying out data rewind; Not existing under the unusual situation, then submit data to.
Preferably, after submitting data to, this method also comprises: return the execution result that the database manipulation order after the encapsulation is called.
Preferably, be under the situation of query manipulation order in the database manipulation order, this method also comprises: judge whether to exist unusual when carrying out the database operational order; Do not exist under the unusual situation, then returning the result who carries out the query manipulation order.
Preferably, the database manipulation order after the encapsulation is called and comprised: the entity class of creating database.
Preferably, the database manipulation order after the encapsulation is called and comprised the following condition that is provided for calling: call the table name of database manipulation order, field and the operation species that needs are operated.
Be described in detail below in conjunction with the implementation procedure of example the embodiment of the invention.
Fig. 2 is the process flow diagram according to the preferred database manipulation process of commands of embodiment of the invention method.
Database manipulation process of commands method of the present invention provides a kind of method for packing of the database manipulation in the face of object, and the inlet for the developer provides unified database manipulation improves efficiency of software, thereby improves the stability of software.Mainly contain four kinds for database manipulation: INSERT, UPDATE, DELETE, SELECT.
As shown in Figure 2, this method comprises the steps:
Step S201 creates entity class.Database receives after the operation requests, creates the entity class of database;
Step S202 is provided with the database table name that needs operation;
Step S203 is provided with the Database field and the value that need inquiry and revise;
Step S204 is provided with condition (when inquiry, modification, deletion);
Step S205, the database data command process is promptly carried out corresponding operating to database;
Step S206 inserts the INSET operational order, changes step S210 afterwards over to;
Step S207 revises the UPDATE operational order, changes step S210 afterwards over to;
Step S208, deletion DELETE operational order changes step S210 afterwards over to;
Step S209 selects the SELECT operational order, changes step S211 afterwards over to;
Step S210 is provided with the database manipulation order and submits to automatically;
Step S211 is combined into SQL statement;
Step S212 is provided with Prepared Statement data;
Step S213 carries out the database operational order;
Step S214, whether the decision operation order has unusually, if change step S215 unusually over to, otherwise, change step S216 over to;
Step S215, the rollback data;
Step S216 submits data to, enters step S217 subsequently;
Wherein, step S218 to step S221 with step S211 to step S214;
Step S221, whether the decision operation order has unusually, if this operational order of abnormal ending, otherwise, change step S217 over to;
Step S217, return results.
Preferably, to these four analyses that database manipulation is realized, the statement analytic process of these four kinds of database manipulations is as follows:
Insert INSERT
The INSERT statement is as follows:
INSERT?INTO?USER(SERID，USERNAME，PASSWORD)
VALUES(100，‘test’，‘test’)
For the Insert statement, mainly be table name, field name, field value, we set up an entity class:
Class EntityClass is the entity class of database table.
Private HashMap＜String, Integer〉intMap=null; The map of // integer field and value
Private HashMap＜String, String〉stringMap=null; The map of // character string field and value
Private HashMap＜String, Date〉dateMap=null; // date field and value.
Private HashMap＜String, Float〉floatMap=null; The private String tableName=null of // floating type field and value; // database table name
By initialization the table name of class is set, expression needs which table of operation, and field value is set again, so just can finish the operation that database is inserted, and can add 1 with automatic generation of database or maximal value for the generation of ID.
Method of operating is:
EntityClass?entityClass＝new?EntityClass(“USER”)；
entityClass.put(“USERID”，”userid”)；
entityClass.put(“USERNAME”，”username”)；
entityClass.put(“PASSWORD”，”password”)；
EntityDAO.getInstance().save(entttyClass)；
Deletion DELETE
The statement of DELETE is as follows:
DELETE?FROM?USER?WHERE?ID＝123
For deletion delete operation, if the condition of a table name and an inquiry, because of also can encapsulating a bit with top entity class.
Method for packing is:
EntityClass?entityClass＝new?EntityClass(“USER”)；
entityClass.setId(123)；
EntityDAO.getInstance().delete(entityClass)；
Deletion for the batch of complexity also can specify a querying condition to delete, and querying condition is seen inquiry SELETE statement, and basic call statement is:
EntityDAO.getInstance () .delete (entityClass, criteria); //criteria is a querying condition.
Revise UPDATE
The statement of Update is as follows:
UPDATE?USER?SET?EMAIL＝’aaa@aaa.com’WHERE?ID＝123
For the update operation, form by three parts of condition of table name, the field name that will upgrade and value, renewal, because of also can encapsulating a bit, encapsulate as follows with top method:
EntityClass?entityClass＝new?EntityClass(“USER”)；
entityClass.put(“EMAIL”，”aaa@aaa.com”)；
entityClass.setId(123)；
EntityDAO.getInstance().update(entityClass)；
Simultaneously, also can specify a querying condition to upgrade for renewal in batches, basic call statement is:
EntityDAO.getInstance () .update (entityClass, criteria); //criteria is inquiry.
Inquiry SELECT
The statement of Select is as follows:
SELECT USERID, USERNAME, EMAIL FROM USER WHEREUSERNAME like=' % king % ';
For the update operation, table name is arranged, the field of inquiry, the condition of inquiry are formed, and also are that field name, condition and field value are formed in the condition of inquiry, so the querying condition class is defined as follows:
Class Condition is the condition class, mainly contains following attribute
Private String fieldname=null; // field name
Private String stringValue=null; The field value of // character string
Private Integer[] inIntList=null; // integer array is used for the in operation
Private String[] inStringList=null; // character string array is used for the in operation
Private Date dateValue=null; The field value on // date
Private Integer intValue=null; The field value of // integer
Private Float floatValue=null; // floating number
Class Criteria is the set of condition, mainly contains following several method:
List＜Condition〉expressionlist=null; The tabulation of // querying condition
List＜Order〉orderlist=null; // sorted lists
Class ConditionGroup condition group can be formed the complicated query condition by ConditionGroup, Condition, three classes of Criteria, satisfies various data base queryings and uses.
Method for packing is as follows:
EntityClass?entityClass＝new?EntityClass(“USER”)；
EntityClass.putField (" USERID "); // the inquiry field is set
EntityClass.putField (" USERNAME "); // the inquiry field is set
EntityClass.putField (" EMAIL "); // the inquiry field is set
Criteria?criteria＝new?Criteria()；
Criteria.add (Expression.like (" USERNAME ", " king ")); // the like querying condition is set
List<EntityClass>
list＝EntityDAO.getInstance().findAll(entityClass，criteria)；
//criteria is a querying condition.
Return results is the tabulation of entity class, for the inquiry of a plurality of tables, can specify a plurality of tables when specifying table name, and Cha Xun entity class also can be specified the SQL condition that several epiphases are handed over simultaneously.
Preferably, this method needs more than the JDK1.5 based on the objectification encapsulation of database manipulation under the JAVA environment, and preferred embodiment is as follows:
Preferably, with tables of data User is increased, deletion, modification, query manipulation be example:
The data structure of table User is:
ID?Number(10，0)NOT?NULL?PRIMARY?KEY，
USERID?VARCHAR2(40)NOT?NULL，
USERNAME?VARCHAR2(40)NOT?NULL，
PAS?SWORD?VARCHAR2(20)NOT?NULL，
EMAIL?VARCHAR2(100)NULL
Increase
Increase data.
EntityClass?entityClass＝new?EntityClass(“USER”)；
entityClass.put(“USERID”，”userid”)；
entityClass.put(“USERNAME”，”username”)；
entityClass.put(“PASSWORD”，”password”)；
entityClass.put(“EMAIL”，”email”)；
EntityDAO.getInstance().save(entityClass)；
Deletion
Delete an ID and be 123 user.
EntityClass?entityClass＝new?EntityClass(“USER”)；
entityClass.setId(123)；
EntityDAO.getInstance().delete(entityClass)；
Delete all surnames " king " user of word.
EntityClass?entityClass＝new?EntityClass(“USER”)；
Criteria?criteria＝new?Criteria()；
Criteria.add (Expression.rightlike (" USERNAME ", " king ")); // the like querying condition is set.
EntityDAO.getInstance().delete(entityClass，criteria)；
Revise
The EMAIL that is 123 user to ID is modified as a.a@a.com.
EntityClass?entityClass＝new?EntityClass(“USER”)；
entityClass.put(“EMAIL”，”aaa@aaa.com”)；
entityClass.setId(123)；
EntityDAO.getInstance().update(entityClass)；
The EMAIL of all surname Wang is modified as a.a@a.com.
EntityClass?entityClass＝new?EntityClass(“USER”)；
entityClass.put(“EMAIL”，”aaa@aaa.com”)；
Criteria?criteria＝new?Criteria()；
Criteria.add (Expression.rightlike (" USERNAME ", " king ")); // the like querying condition is set.
EntityDAO.getInstance().update(entityClass，criteria)；
Inquiry:
Inquire about the user of all surname Wang:
EntityClass?entityClass＝new?EntityClass(“USER”)；
EntityClass.putField (" * "); // the inquiry field is set.
Criteria?criteria＝new?Criteria()；
Criteria.add (Expression.rightlike (" USERNAME ", " king ")); // the like querying condition is set.
List<EntityClass>
list＝EntityDAO.getInstance().findAll(entityClass，criteria)；
//criteria is a querying condition.
If there are user's out of Memory such as age in another one table (USERINFO), this table has two fields:
ID?NUMBER(10，0)NOT?NULL，
AGE?NUMBER(3，0)NOT?NULL
Call method is as follows:
EntityClass?entityClass＝new?EntityClass(“USER，USERINFO”)；
entityClass.setJoinCondition(“USER.ID＝USERINFO.ID)；
EntityClass.putField (" AGE "); // the inquiry field is set
EntityClass.putField (" USERNAME "); // the inquiry field is set
EntityClass.putField (" USERID "); // the inquiry field is set
EntityClass.putField (" PASSWORD "); // the inquiry field is set
Criteria?criteria＝new?Criteria()；
Criteria.add (Expression.rightlike (" USERNAME ", " king ")); // the like querying condition is set.
List<EntityClass>
list＝EntityDAO.getInstance().findAll(entityClass，criteria)；
//criteria is a querying condition.
From above description, as can be seen, the present invention has realized following technique effect: the disposal route of utilizing the objectification of existing techniques in realizing database data order, the developer can grasp the programming to database fast, improve the efficient of programming, guarantee the reusability of data Layer operation, thereby improve the stability of software.Comprise the operational order of database is carried out unified encapsulation, thus the reusability of assurance database manipulation layer, the stability of assurance system; The developer can just can finish the operation of database regardless of the SQL grammer; PreparedStatement is all used in all operations, improves the performance of database manipulation; Call simply, easily left-hand seat; The integration environment is simple; Support any complicated query.
According to embodiments of the invention, provide a kind of database manipulation process of commands device.
Need to prove, can in computer system, carry out in the step shown in the process flow diagram of accompanying drawing such as a set of computer-executable instructions, and, though there is shown logical order in flow process, but in some cases, can carry out step shown or that describe with the order that is different from herein.
Fig. 3 is the synoptic diagram according to the treating apparatus of storehouse operational order according to the embodiment of the invention.
As shown in Figure 3, this device comprises: package module 301 and calling module 302.
Package module 301 encapsulates the database operational order;
Calling module 302 is used for the described database manipulation order after the encapsulation is called.
Preferably, described treating apparatus also comprises: judge module 303.
Judge module 303, be used for judging when carrying out described database manipulation order, whether exist unusual.
Obviously, those skilled in the art should be understood that, above-mentioned each module of the present invention or each step can realize with the general calculation device, they can concentrate on the single calculation element, perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in the memory storage and carry out by calculation element, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. a database manipulation process of commands method is characterized in that, comprising:
The database operational order is encapsulated;
Described database manipulation order after the encapsulation is called.
2. disposal route according to claim 1 is characterized in that, before the database operational order was encapsulated, described method also comprised:
Receive described database manipulation order.
3. disposal route according to claim 1 is characterized in that, described database manipulation order comprises one of following kind:
Insert operational order, retouching operation order, deletion action order, query manipulation order.
4. disposal route according to claim 3 is characterized in that, is that described method also comprises under the situation of one of described insertion operational order, described retouching operation order and described deletion action order in described database manipulation order:
When carrying out described database manipulation order, judge whether to exist unusual;
Exist under the unusual situation, then carrying out data rewind;
Not existing under the unusual situation, then submit described data to.
5. disposal route according to claim 4 is characterized in that, after submitting described data to, described method also comprises:
Return the execution result that the described database manipulation order after the encapsulation is called.
6. disposal route according to claim 3 is characterized in that, is under the situation of query manipulation order in described database manipulation order, and described method also comprises:
When carrying out described database manipulation order, judge whether to exist unusual;
Do not exist under the unusual situation, then returning the result who carries out described query manipulation order.
7. disposal route according to claim 1 is characterized in that, the described database manipulation order after the encapsulation is called comprise:
Create the entity class of database.
8. disposal route according to claim 1 is characterized in that, the following condition that is provided for calling that comprises is called in the described database manipulation order after the encapsulation:
Call the table name of described database manipulation order, field and the operation species that need operate.
9. a database manipulation process of commands device is characterized in that, comprising:
Package module encapsulates the database operational order;
Calling module is used for the described database manipulation order after the encapsulation is called.
10. treating apparatus according to claim 9 is characterized in that, described treating apparatus also comprises:
Judge module, be used for judging when carrying out described database manipulation order, whether exist unusual.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102442072A CN102110111A (en) | 2009-12-29 | 2009-12-29 | Method and system for processing database operating command |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102442072A CN102110111A (en) | 2009-12-29 | 2009-12-29 | Method and system for processing database operating command |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102110111A true CN102110111A (en) | 2011-06-29 |
Family
ID=44174274
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009102442072A Pending CN102110111A (en) | 2009-12-29 | 2009-12-29 | Method and system for processing database operating command |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102110111A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102346774A (en) * | 2011-09-26 | 2012-02-08 | 深圳市信游天下网络科技有限公司 | Database operation method and device |
| CN102360385A (en) * | 2011-10-14 | 2012-02-22 | 盛乐信息技术（上海）有限公司 | File searching method and system |
| CN103577560A (en) * | 2013-10-24 | 2014-02-12 | 华为技术有限公司 | Method and device for inputting data base operating instructions |
| CN103838574A (en) * | 2014-02-20 | 2014-06-04 | 浪潮集团山东通用软件有限公司 | General method for grouped summarizing of data tables |
| CN104915383A (en) * | 2015-05-19 | 2015-09-16 | 中国电子科技集团公司第二十八研究所 | General method for automatic object adapting in database access |
| CN106528256A (en) * | 2016-10-20 | 2017-03-22 | 国云科技股份有限公司 | Java EJB (Enterprise Java Bean) platform based entity BEAN general query method |
| CN106610973A (en) * | 2015-10-21 | 2017-05-03 | 北京国双科技有限公司 | Television data query method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1881242A (en) * | 2005-06-14 | 2006-12-20 | 张晓东 | Trans-enterprise supply chain system WEB application platform for automobile industry |
| CN101110030A (en) * | 2007-08-23 | 2008-01-23 | 南京联创科技股份有限公司 | Developing method for data base persistence layer based on JAVA |
| CN101256650A (en) * | 2008-03-21 | 2008-09-03 | 中国科学院软件研究所 | Method and system for extracting enterprise data based on service entity |
-
2009
- 2009-12-29 CN CN2009102442072A patent/CN102110111A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1881242A (en) * | 2005-06-14 | 2006-12-20 | 张晓东 | Trans-enterprise supply chain system WEB application platform for automobile industry |
| CN101110030A (en) * | 2007-08-23 | 2008-01-23 | 南京联创科技股份有限公司 | Developing method for data base persistence layer based on JAVA |
| CN101256650A (en) * | 2008-03-21 | 2008-09-03 | 中国科学院软件研究所 | Method and system for extracting enterprise data based on service entity |
Non-Patent Citations (1)
| Title |
|---|
| 未知: "《使用XML封装数据库操作语句的实现》", 24 June 2005, HTTP://XIAORUANJIAN.ITEYE.COM/BLOG/1375221 * |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102346774A (en) * | 2011-09-26 | 2012-02-08 | 深圳市信游天下网络科技有限公司 | Database operation method and device |
| CN102346774B (en) * | 2011-09-26 | 2013-09-18 | 深圳市信游天下网络科技有限公司 | Database operation method |
| CN102360385A (en) * | 2011-10-14 | 2012-02-22 | 盛乐信息技术（上海）有限公司 | File searching method and system |
| CN103577560A (en) * | 2013-10-24 | 2014-02-12 | 华为技术有限公司 | Method and device for inputting data base operating instructions |
| CN103838574A (en) * | 2014-02-20 | 2014-06-04 | 浪潮集团山东通用软件有限公司 | General method for grouped summarizing of data tables |
| CN104915383A (en) * | 2015-05-19 | 2015-09-16 | 中国电子科技集团公司第二十八研究所 | General method for automatic object adapting in database access |
| CN104915383B (en) * | 2015-05-19 | 2018-03-02 | 中国电子科技集团公司第二十八研究所 | A kind of method of automatic adaptation object during Universal Database accesses |
| CN106610973A (en) * | 2015-10-21 | 2017-05-03 | 北京国双科技有限公司 | Television data query method and device |
| CN106528256A (en) * | 2016-10-20 | 2017-03-22 | 国云科技股份有限公司 | Java EJB (Enterprise Java Bean) platform based entity BEAN general query method |
| CN106528256B (en) * | 2016-10-20 | 2019-06-21 | 国云科技股份有限公司 | A kind of entity B EAN general polling method based on Java EJB platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102110111A (en) | Method and system for processing database operating command | |
| CN104573115B (en) | Support the realization method and system of the integrated interface of multi-type database operation | |
| US5878411A (en) | Dependent object class and subclass mapping to relational data store | |
| US6240422B1 (en) | Object to relational database mapping infrastructure in a customer care and billing system | |
| CA2259544C (en) | Extensible indexing | |
| US8166070B2 (en) | Techniques for sharing persistently stored query results between multiple users | |
| CN100557609C (en) | A kind of persistent layer generation method and device | |
| US8775470B2 (en) | Method for implementing fine-grained access control using access restrictions | |
| CN102129539A (en) | Data resource authority management method based on access control list | |
| US8682912B2 (en) | Providing secure access to data with user defined table functions | |
| TW200412515A (en) | Row-level security in a relational database management system | |
| WO1999052044A1 (en) | A system and method for accessing data stores as objects | |
| CN100397397C (en) | XML data storage and access method based on relational database | |
| Yaseen et al. | An extensible kernel object management system | |
| US7054862B2 (en) | Method and system for long-term update and edit control in a database system | |
| CN114138878A (en) | JAVA general edition relational data operation middleware | |
| Harrison et al. | Languages and programming interfaces | |
| Hu et al. | Implicit authorization mechanism of object-oriented database | |
| Jungmann et al. | Advanced Object-Relational Mapping | |
| Rosenthal et al. | Granularity of Data Protection for MLS Applications and DBMSs. | |
| Roche et al. | Using the App Engine Datastore | |
| Subramaniam | A mediator-based approach to support ECA rules in DB2 | |
| Chen | Interface Between Object-Oriented Databases And Relational Databases Using B-Tree Object-Relational Access Interface | |
| Keith et al. | Advanced Object-Relational Mapping | |
| Schlegelmilch | Role-based persistence |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20110629 |