CN102693295B

CN102693295B - Database record data query system based on record logical representation

Info

Publication number: CN102693295B
Application number: CN201210151284.5A
Authority: CN
Inventors: 龙毅宏; 唐志红; 杨浩; 肖凡; 刘旭; 白波
Original assignee: BEIJING ITRUSCHINA Co Ltd; Wuhan University of Technology WUT
Current assignee: BEIJING ITRUSCHINA Co Ltd; Wuhan University of Technology WUT
Priority date: 2012-05-15
Filing date: 2012-05-15
Publication date: 2014-01-01
Anticipated expiration: 2032-05-15
Also published as: CN102693295A

Abstract

The invention relates to a database record data query system based on record logical representation. The database record data query system comprises a logical record definition and mapping component, a named relation and limited class defining component, a logical record query component, a record relation expansion sub-process and a record database. Several thoughts and methods of logical representation are used for data query of a common database without using the complicated implementation technology of the logical representation. A user of data can define logical records aiming at the data in the database according to self needs, and converts record logical representation record query conditions or commands into database query SQL (structured query language) statements by corresponding relations between logical records and database records; and the user can self-define record named relations and record limited classes by recording named relation definition rules, and uses record naming and the record limited classes in record query condition expressions or commands to enable the expressions of the record query conditions to be simpler.

Description

A kind of data-base recording data query system based on recording logical expressions

Technical field

The invention belongs to electronical record and database technical field, especially, is a kind of data-base recording data query system based on recording logical expressions.

Background technology

Relational database (relational database) is widely used in storing various application datas.A relational database is comprised of one or more database table (database table), wherein database table is comprised of row (array) again, and row is comprised of a plurality of fields (field) or row (column), application data finally is kept in the respective field of corresponding line of (one or more) database table.Be kept at data in database table also referred to as record (record).The data recording be kept in the disparate databases table can associate by certain mode a larger data recording of formation, perhaps form the record with certain incidence relation, the former is corresponding to a situation record is kept in multiple different tables, the latter is corresponding to the situation that has incidence relation between different pieces of information record (as, the incidence relation between a patient's electronic health record record records with its electronic verification certificate).Incidence relation between identical or different types of record is called the relation of record.

That relational database system adopts the inquiry that is kept at the record data that meet certain condition or relation in database is SQL(Structured Query Language) statement, used SQL statement data query record to have following limitation or shortcoming:

1) need direct usage data storehouse table and field thereof to be inquired about, need know the structure of database table, be not suitable for the general population

The direct usage data of SQL storehouse table, data sheet field mean querying condition, directly use mutual relationship between the field of showing (as >,<,=etc.) mean the relation between data recording; When record data are kept in multiple disparate databases tables, these database tables need to be connected to (join) and get up to inquire about and will combine from the Query Result of disparate databases table (being about to the Query Result integration for the record field of disparate databases table).This record queries condition, the expression way that records relation and Query Result array mode, when using, the user need to know the structure of database table, and only be suitable for acquaint with data storehouse technology, have the professional and technical personnel of relevant professional knowledge, domestic consumer can't be used at all.In fact, concerning the general population, the record data (being called logical record) that the logic level often that they are concerned about or abstract aspect mean, as someone information such as name, age, work unit, they are indifferent to the concrete Storage Format (physical record data in database) of record data at database; Use the domestic consumer of record data when expression meets recording of some conditioned disjunction relation, often with the recorded information (data) of logic level or abstract aspect express correlated condition (as the age be greater than the people of 20 years old identity information, there is same father and mother's people's identity information), rather than (because what they are ignorant of even at all, be database with the physical record in database table! ).

2) can only be inquired about for fixing record data content by man-machine interface, be lacked dirigibility

Because being not suitable for domestic consumer, uses SQL, therefore, the special human-computer interaction interface that domestic consumer can only provide by Data application system, by given mode, fixing record data content is inquired about, can not, according to oneself needing self-defined inquiry object, inquiry mode, be lacked dirigibility.

3) can not inquire about the record that is mutually related by naming relationship (named relation)

Based on SQL statement, can only mean by the numerical relation between the record field of database table the relation between record (two or more), and inquiry, obtain the record that meets given relation, the combination of record data in record data and B in the A equated with the value of field B in table 2 as the value that meets the field A in table 1 in table 1 and table 2, perhaps meet the associated record from table 1 and table 2 of this relation, can not mean the relation between many records by concerning intuitively title, and inquiry, obtain the record that meets this kind of relation, as the electronical record combination of satisfied " same people " relation in electronic health record record and blood test list etc.

Purpose of the present invention will overcome the above problems exactly.Logical expressions are a kind of basic modes of the representation of knowledge, can be in the knowledge of this basic representation complexity, carry out reasoning from logic, the solution of the present invention has been used some thinking of the representation of knowledge, as by the rule definition relation, but logical expressions of the present invention and common logical expressions (being the representation of knowledge) are theoretical different with method, be mainly reflected in following some:

1) data recording in database is not the descriptor as Object of Knowledge, but, using itself as Object of Knowledge, each data field of record data is its descriptor;

2) relation between the example that different Object of Knowledge are concrete is not kept in database as knowledge;

3) related Object of Knowledge (recording class and the example) is not that be scheduled to, fixing, but database user need to define for the data in database oneself according to own;

4) data in relational database are not had to special form, location mode requirement, be suitable for common relation data database data, the application data be kept in relational database need to not made change in order to use this method and system.

5) finally on technology realizes, technical scheme of the present invention is not used the complex technology of logical expressions/representation of knowledge (as Web Ontology/Resource Description Framework, OWL/RDF), do not use relevant technical tool (as the OWL/RDF instrument) yet; But by simply recording inquiry, the search of the Mapping implementation record data (knowledge) between contextual definition and expansion process, abstract record data and data-base recording data.

Summary of the invention

The objective of the invention is: the user who proposes a kind of database data record can need the self-defining data database data to record the abstract classification of object and domestic consumer according to application can be accordingly by the self-defined relation that records of man-machine interface, to comprise naming relationship and using this as the required record data of record queries condition query and, without the data-base recording data query system based on recording logical expressions of being concerned about record data concrete Storage Format and mode in database, described naming relationship is the denominative relation that records of tool.

To achieve these goals, the technical solution adopted in the present invention is:

A kind of data-base recording data query system based on recording logical expressions, described record logical expressions be a kind of information content comprised with record relevant and with the concrete file layout of record data, mode and location-independent a kind of record data representation or expression way, the record meaned by this form or mode is called logical record; In logical record, a record that comprises concrete data is called the logical record example, is called for short record instance; Be called a logical record class for same purpose, set with logical record example of same alike result; Physical record data corresponding with logical record, that be kept in database are called physical record; Record the set (subset) that meets the record instance of certain qualified relation in the record instance set of class and form a new class that records, be called the former restriction class that records class, or record limits class or restriction and records class or be called for short and limit class (unless specialized, the following stated records class, record instance, record and closes logical record class, logical record example, the logical record relation of meaning).

Described system comprises logical record definition and map component, naming relationship and restriction class definition assembly, logical record enquiring component, the relation that records is launched subprocess, database of record, wherein:

Logical record definition and map component: a functional module with human-computer interaction interface, the data administrator carries out abstract logical expressions by this assembly to the record data that are kept in relational database, define corresponding logical record class, and the corresponding relation between logical record data and database data or mapping relations;

Naming relationship and restriction class definition assembly: a functional module with human-computer interaction interface, domestic consumer records the naming relationship definition rule by this assembly input logic, the definition record naming relationship, and by the restriction class of the existing logical record class of this component definition;

The logical record enquiring component: a functional module with human-computer interaction interface, the record queries condition that domestic consumer means by the logical record relation by this assembly input, inquire about, obtain the logical record data that satisfy condition;

The relation that records is launched subprocess: in the record data query script, by the logical record enquiring component, called, logic-based records the naming relationship definition rule or limits the class definition rule, launch, replace the naming relationship and/or the record that record in relational expression and limit class, make final as recording in relational expression of record queries condition do not comprise naming relationship and/record limits class;

Database of record: the relational database system of depositing the physical record data.

Described logical record definition defines logical record as follows with map component, and the corresponding relation between logical record data and database physical record data:

The 1st step: define a logical record class and unique name thereof and/or sign (ID);

The 2nd step: define record field that the record instance of described logical record class comprises and the type (as word string, text, byte, integer, date, time etc.) of each field;

The 3rd step: define the corresponding relation of described logical record class and database table, comprise the title of one or more database table that described logical record class is corresponding;

The 4th step: define corresponding relation or mapping relations between the field of record field and described corresponding database table of record instance of described logical record class;

The 5th step: the interrelational form (as interrelated as which field by database table) between definition Relational database table.

Different logical record classes and the corresponding database table of record instance thereof and data sheet field can be identical, also can be different; Described logical record example has one in affiliated title unique in recording class or sign, to represent oneself; The logical record example can be by the value (as the title that records main body, the identification number of correspondence) of certain record field in its record data as its title or sign, or by the derivation value of record field as its title or sign; For a definite or known logical record example, its title is a definite constant be comprised of word string, be called logical record instance name constant (or constant title, determine title), corresponding logical record example is called constant logical record example, in the record queries condition, logical record instance name constant represents this determine, known logical record example; For logical record example uncertain or undetermined, its title is a non-quantitative (the interior perhaps value that is title is uncertain), with a variable name, replace, be called logical record instance name variable, corresponding logical record example is called variable logical record example, when carrying out the record data inquiry, logical record instance name variable represents needs obtain, the one or more logical record examples that meet querying condition of inquiry.

Relation between the described record field that records relation or logical record example and constant value, or the field relation between two logical record examples, or the naming relationship between two logical record examples, or the logic "and" operation of these relations combination; Wherein, relation between the record field of described logical record example and constant value, be numerical relation between record field and constant value (as >,<,=, unequal to), comprise following information in its expression formula: the title that records class name, logical record example of logical record example, the relevant field name of logical record example and the numerical relation between this field and constant value (as, the value of the field a of the record instance X of logical record class A equals 123); Field relation between described two logical record examples, i.e. numerical relation between the record field of two logical record examples, comprise following information in its expression formula: the title that records class name, interrelated logic record instance of interrelated logic record instance, the relevant field name of interrelated logic record instance, and the numerical relation between the record field of interrelated logic record instance (as the value of the field a of the record instance X of logical record class A equals the value of field b of the record instance Y of logical record class B); Field relation between the record field of logical record example and constant value between relation and two logical record examples is referred to as logical record instance field relation; Naming relationship between two logical record examples, the relation between two record instances that mean with naming relationship, its expression formula comprises following information: the interrelated logic record instance record class name, the title of interrelated logic record instance, and the title of naming relationship between the interrelated logic record instance; Appear at logical record example or constant logical record example in the relation of record, or variable logical record example; If the logical record example appeared in the relation of record is constant logical record example, its title is used the title constant; If the logical record example appeared in the relation of record is variable logical record example, its title is used the title variable; In recording relational expression, by corresponding mode, distinguish title constant and title variable (as the variable name front at the title variable adds a question mark); Each composing factor (Element) in described logical operation combination of recording relation, be the naming relationship between the field relation between relation or two record instances or two record instances between the record field of variable logical record example and constant value, be called the factor that concerns that records relational expression; Describedly concern that the logic evaluation value of the factor is "true" or "false".

Naming relationship and restriction class definition assembly are used the naming relationship between following naming relationship definition rule definition logical record example:

If two logical record examples also meet the given relation that records by relevant intermediate logic record instance, there is defined naming relationship between these two logical record examples so.

In described contextual definition rule " if " statement is corresponding to rule condition, result is set up needs satisfied prerequisite; " so " statement in described contextual definition rule is corresponding to regular result, the naming relationship that will define; Two logical record examples that occur in the condition of described rule the given relation that records that need to meet by relevant intermediate logic record instance (" if " in the relation that records) be called the conditional relationship (be called for short rule condition relation) of naming relationship definition rule; At least one is variable logical record example for two logical record examples in the result of described naming relationship definition rule (i.e. " so "); Intermediate logic record instance in the conditional relationship of described naming relationship definition rule, that finger occurs in the rule condition relation and in rules results absent variable constant or variable logical record example (such as relation rule: if the value of the field a of the record instance X of logical record class A equals the value of field b of the record instance Y of logical record class B, and, the value of field c that records the record instance Y of class B equals to record the value of field e of the record instance Z of class C, so the record instance X of logical record class A and record between the record instance Z of class C and exist and concern R; The Y here is exactly extra, title variable intermediate variable logical record example of introducing while concerning between definition record instance X and record instance Z); Recording the title variable of the logical record example occurred in the contextual definition rule, comprise title variable extra, the intermediate variable record instance, is inessential for the definition of recording relation and expression; Can use other defined naming relationships in the conditional relationship of the definition rule of a naming relationship, but the naming relationship itself that directly or indirectly service regeulations will define, can not recursive definition; A naming relationship can define with many described naming relationship definition rules, between many rules, is the relation of logical "or",, as long as a rule is satisfied, between two record instances, has corresponding naming relationship.

Described naming relationship provides record to limit the defined function of class with restriction class definition component internal by following special logical record naming relationship definition rule:

If the variable record instance of certain already present logical record class also meets the given relation that records by other intermediate logic record instances, this variable logical record example has predetermined naming relationship with any example that the record that will define limits in class so: belong to the same class that records;

Wherein, the given relation that records is the qualified relation to record instance in described logical record class; Described record limits the variable logical record case representation (meaning as used title variables A NY) with special title variable for any record instance of class; The title variable (as ANY) of the variable logical record example of any record instance of described expression does not appear in the expression formula of rule condition relation; Based on the described naming relationship definition rule that records especially, allly meet this corresponding record instance of variable record instance that " belongs to the same class that records " and record relation and formed the already present restriction class that records class that will define; Limiting class definition can be nested, in defined restriction, records on the basis of class further definition record and limits class; But limiting class definition can not recurrence, in the rule condition of definition rule, can not comprise directly or indirectly the restriction class itself that will define.

The above special contextual definition rule, only used in naming relationship and restriction class definition component internal; In naming relationship and restriction class definition assembly outside, it is user interface layer, directly do not use, the user only need input following information by special interface when definition record limits class: former class name, the restriction class name that define that records class of the definition class, mean former record class in title variable and the satisfied given relation that records of needs thereof of variable logical record example.

Described logical record enquiring component is according to recording record queries condition query that relation means, obtaining the record that required record comprises separately or exist incidence relation, i.e. inquiry obtain with variable logical record example representative, can make the described relation establishment of recording, all logical record examples that the result that makes the logical combination computing of the relation of record is "True".

Described logical record enquiring component is as follows according to using the record queries condition that relation means that records, and required record data are obtained in inquiry:

Step I: by calling one, record relation expansion subprocess (subroutine, function) will mean that naming relationship or record that recording of record queries condition comprises in relation limit the expansion of class record instance expression formula, obtain the set of relations that records of an expansion, each in set of relations is all the formed relation that records of logic "and" operation combination that concerns the factor that the field relation by the logical record example of non-limiting class means, record the field relation between the record field that concerns the factor or variable logical record example of relation and the relation between constant value or two logical record examples, and concern in the factor and do not exist record to limit the logical record example that class means,

Step II: successively each in set of relations of recording of the described expansion in step I is recorded to the operation of relation as record queries condition execution step III to step IV, return results after completing processing;

Step II I: according to corresponding relation or the mapping relations between the physical record data in the record data of logical record and database, using only comprise logical record field relation, become the record queries condition meaned by the database table field in database and generate corresponding SQL statement as the transformation that records of record queries condition;

Step IV: based on the III step, transform the SQL statement Query Database generated, then physical record data result data base querying obtained changes into the logical record data, and the logical record data that obtain are merged in Query Result final, that need to return.

The described relation expansion subprocess that records that described logical record enquiring component calls at step I has following suction parameter:

Input parameter:

1) the to be launched relation that records;

2) in the middle of, the title variograph is counted object, a data object that comprises the integer count value, word string value corresponding to this count value inserted to be added to record to be concerned in introduce in expansion process extra, title variable intermediate variable logical record example, to distinguish different middle title variablees or intermediate variable logical record example;

Output parameter:

That 1) has launched records set of relations, by " suitable " that obtain after the relation that records of launching is launched of input, comprise a plurality of set of relationship that record that record relation.

The described relation expansion subprocess that records is operated as follows:

Step 1: each record in relation to be launched of scanning input concerns the factor successively, once surface sweeping runs into one, means with naming relationship or comprise that record limits the factor that concerns of class record instance, proceeds to step 2; Do not run into if scanned with naming relationship and mean or comprise the factor that concerns that record limits the class record instance, the to be launched relation that records that directly will input joins recording in set of relations that output parameter launched, then return results (Output rusults only comprises one and records relation, i.e. the to be launched relation that records of input);

Step 2: if the need that step 1 scanning is met are to be processed, concern that the factor is the relation that records between two record instances that mean with naming relationship, this naming relationship is replaced with the conditional relationship of its naming relationship definition rule, otherwise the factor that concerns that limits the class record instance to comprising record is handled as follows: the record that first will appear at the restriction logic of class record instance concerned in factor expression limits class and substitutes by the corresponding former class that records, and then will record the conditional relationship limited in the class definition rule and join concerning in the factor of replaced processing by logical “and”; In the alternate process process, title constant or the title variable of the logical record example that concerns the correspondence in the factor that the title variable of the correlated variables logical record example in the rule condition relation of being used as to substitute is being processed substitute; For extra, title variable intermediate variable logical record example replaced in the rule condition relation of introducing in expansion process, word string value corresponding to the count value of middle title variograph being counted to object according to predetermined mode joins that this is extra, in the variable name of title variable intermediate variable logical record example; Limit the corresponding a plurality of naming relationship definition rules of logic of class record instance if substitute described naming relationship or the record of expansion, alternative with the conditional relationship of each contextual definition rule respectively, obtain the factor that concerns after a plurality of alternative expansion;

Step 3: the factor that concerns after the one or more expansion that obtain after step 2 alternate process is combined by logical “and” with the factor that concerns not yet scanned of remainder respectively, obtain one or more interim, middle to be launched relations that record; Generate a set with all interim, middle to be launched relations that record that obtain through this processing;

Step 4: the count value that middle title variograph is counted in object adds 1;

Step 5: each record in set of relations interim, middle to be launched of taking out successively that step 3 produces records relation, the processing of execution step 6-7; After completing processing, return results;

Step 6: call the relation that records and launch subprocess self (being recursive call self), it is that of taking out from interim, intermediate record set of relations in step 5 records relation that input parameter while calling record to be launched closes, and in the middle of input parameter, the title variograph is counted the middle title variograph that object is current implementation and counted object;

Step 7: to calling the relation that records in step 6, launch the set of relations that records that output parameter that subprocess returns launches and be handled as follows: non-name relation table scanned in current implementation step 1 is shown or do not comprise each in set of relations of recording that limit the class record instance all concern the factor and the expansion of returning and record relation and merges and form the accordingly new relation that records by logic "and" operation, and the new relation that records after all merging is joined to recording in set of relations that the output parameter of current implementation launched.

If the need that scan in described step 1 are to be processed concern the factor be one with naming relationship, mean concern the factor simultaneously and one comprise the factor that concerns that record limits the class record instance, what in described step 2, only by naming relationship, mean concerns factor treatment.

In the described relation that records, launch during subprocess launches to record the process of relation, for can determine its logic evaluation value be "True" concern the factor (as the field relation of two constant logical record examples), the replacement of use logical value "True"; For comprising the relation that records that concerns the factor that the logic evaluation value is " vacation ", directly use logical value " vacation " to replace.

Described logical record enquiring component calls described when recording relation and launching subprocess at step I, the relation that records that input parameter is to be launched is the relation that records as the record queries condition, and to count the count value of object be predetermined initial value (as 0 or 1 etc.) to the title variograph in the middle of input parameter.Described, record during relation launches the recursive call process of subprocess, in the middle of the input parameter of transmission title variograph number to as if same data object (as the same C/C++ data object pointed to by data pointer or the same Java object pointed to by object reference).

Word string value corresponding to the count value that middle title variograph is counted to object described in described step 2 joins described predetermined mode in the title variable of replacing extra, the middle variable logical record example in the rule condition relation of introducing in expansion process without special regulation, as long as make the title variable extra, intermediate variable logical record example of introducing in expansion process not repeat with the title variable of its dependent variable logical record example.

The described relation that records is launched subprocess by following Function Extension, described to be launched the recording in relation as the record queries condition of inputting while allowing the logical record enquiring component to call described subprocess, in the conditional relationship of the definition rule of naming relationship, logical "or" and/or the NOT operation combination of the factor appear concerning perhaps:

If there is the logical "or" computing that concerns the factor as recording in relation of querying condition, the relation that this recorded be decomposed into a plurality of relations that record that do not comprise the logical "or" computing (decomposition of then usining respectively obtain each record relation as querying condition inquiry obtain data, finally will inquire about and obtain the result merging);

If have the logic NOT operation for the logic evaluation value of logical record instance field relation as recording in relation of querying condition, by this logic NOT operation for logical record instance field relation substitute (as the field relation by record instance " equals " to become " being not equal to ", " being less than " becomes " being not less than ") together with the NOT operation logical operator by the of equal value logical record instance field relation that does not comprise the NOT operation logical operator;

If there is the logical "or" computing that concerns the factor in the rule condition relation as the naming relationship definition rule, this rule condition relation is decomposed into to a plurality of relations that record that do not comprise the logical "or" computing, then the decomposition of usining obtains each and records the rule condition relation of relation as the naming relationship definition rule, and obtaining a plurality of is the naming relationship definition rule of "or" relation each other;

If as the logic NOT operation of subsistence logic record instance field relation in the rule condition relation of naming relationship definition rule, by this logic NOT operation for logical record instance field relation together with the NOT operation logical operator, by the of equal value logical record instance field relation that does not comprise the NOT operation logical operator, substitute.

Described logical record enquiring component is set according to corresponding querying command, not only can inquire about and obtain the corresponding all logical record examples of variable logical record example that making the relation that records set up, and can return and make the relation of record set up required all intermediate logic record instances.

Innovation of the present invention is: the inquiry by some thinkings of logical expressions and method for the data-base recording data has proposed a kind of universal method and the system of the relational database record data inquiry based on recording logical expressions; The method and system be by meaning the corresponding relation between record queries condition and definition logical record data and database physical record data with logical record, make the expression of record queries conditioned disjunction order can be used by domestic consumer; By recording the introducing of naming relationship, record restriction class, make the expression of record queries condition simpler; Although the method and system have been used part thinking and the method for logical expressions, do not adopt the complex technology of logical expressions.

The accompanying drawing explanation

Fig. 1 is one-piece construction figure of the present invention.

The realization flow figure that Fig. 2 is logical record enquiring component of the present invention.

Fig. 3 A-Fig. 3 B is the realization flow figure that relation is launched subprocess that records of the present invention.

Embodiment

Below in conjunction with accompanying drawing, the present invention is described in further detail.

The present invention is a kind of data-base recording data enquire method and system based on recording logical expressions, the one-piece construction of system of the present invention as shown in Figure 1, filled arrows mean the user to, hollow arrow means that data generate direction, wherein, it is functional module that the logical record definition launches subprocess S4, database S5 with map component S1, naming relationship and restriction class definition assembly S2, logical record enquiring component S3, the relation that records, and other are related data.In figure, the effect of each element and function are discussed in summary of the invention in front, at this, do not repeat, and the mutual relationship between each key element is briefly described as follows:

The data administrator is by using the definition of (T1) logical record and map component S1, for the record data in database S5 (physical record), S6 carries out abstract representation (T2), produce (G1) logical record S7(and comprise logical record class and the example), produce the mapping relations S8 between (G2) logical record and data-base recording; Concern between logical record instance field and constant value that S9 is used (T3) logical record S7; Field between two logical record record instances concerns that S10 is used (T4) logical record S7; The user uses (T5) naming relationship and limits class definition assembly S3 input (G3) naming relationship definition rule S11; Naming relationship definition rule S11 is used between (T6, T7, T8) logical record instance field and constant value the field concerned between S9, two logical record record instances to concern S10 and defined logical record example naming relationship S12, perhaps define, produce the logical record example naming relationship S12 that (G4) is new, or definition, produce the restriction class (new record class) of (G5) existing logical record class; The recording of logical record example concerns that S13 is with concerning between (T9, T10, T11) logical record instance field and constant value that the field between S9, two logical record examples concerns that the logical operation combination of S10, logical record example naming relationship S12 means; The user, by (T12) logical record enquiring component S3, uses (T13) to record and concerns that S13 is as querying condition query note data; Logical record enquiring component S3 is when recording the relational query record data, and (T14) relation of calling is launched subprocess S4; Relation is launched subprocess S4 and is used (T15) to record contextual definition rule S11, perhaps the naming relationship recorded in relation is replaced, is launched to process, perhaps to recording restriction class in relation, replaced, launched to process, make the relation that records as the record queries condition after replacements, expansion only comprise the field relation of logical record example; Afterwards, logical record enquiring component S3 utilizes (T16) logical record and physical record mapping relations S8, and the record queries condition and the name that only comprise logical record instance field relation are changed, and generates (G5) data base querying SQL statement S14; Then usage data library inquiry SQL statement S14 inquires about, obtains the physical record data S6 in (T18) database S5, then the record data of inquiry is represented to the user by the form of (T19) logical record.

After above relationship description has been arranged, the concrete enforcement of content of the present invention relates generally to: the expression of Various types of data, and logical record defines and map component S1, naming relationship and restriction class definition assembly S2, logical record enquiring component S3, the relation that records are launched the enforcement realization of subprocess S4, below with regard to their concrete enforcement, describes respectively.

Described Various types of data mainly comprises: logical record (comprise and record class, record instance) definition data, the data of description of logical record data (field of logical record example) and data-base recording data (database table and field) corresponding relation, the logical record instance data, record relation table registration certificate, record contextual definition Rule Expression data.All these data representations divide two aspects: system is processed aspect, user interface aspect.The tables of data first finger of described system processing aspect is kept at can be by the data representation format of computer system processor in internal memory, file and/or database; That the tables of data first finger of described user interface top layer face is seen by the human-computer interaction interface of computing machine or write on the data representation format above paper medium.

Data of description for definition data, logical record data and the data-base recording data corresponding relation of described logical record, no matter in system, process aspect, or at user's interlayer face, it is concrete implements that there is no particular limitation, as long as specific embodiments can reflect content described in table 1, table 2 and the information of expression: table 1 for example understands logical record class of definition, record instance field, and description record field and the required content of database table corresponding relation; Table 2 is for example clear associates required content and information (the User table in database is associated by their field UID with the AddressTable table in database, and the field in certain two tables can be not of the same name) by two database tables.

Table 1 logical record (class, example) definition reaches with the mapping relations of data-base recording data and describes

The incidence relation of table 2 database table

Database table 1	Table 1 associate field	Database table 2	Table 2 associate field
				User	UID	AddressTable	UID

Similarly, expression for the logical record instance data, no matter in system, process aspect, or at user's interlayer face, it is concrete implements that there is no particular limitation, as long as specific embodiments comprises following information to the expression of logical record instance data: the corresponding data that records class, record instance title, the record field comprised and field under record instance.In the data representation of logical record example, need to distinguish that data content is known by certain mode, definite record instance (constant record instance) and content the unknown, uncertain record instance (variable record instance), such as in the data structure that means record instance in internal memory, meaning, distinguish these two kinds different logical record examples with a sign; At user interface layer, can add in the variable name front of the title variable of record instance a denoting contents the unknown, do not lack fixed record instance.

Similarly, for recording relation table registration certificate, recording contextual definition Rule Expression data, no matter in system, process aspect, or at user's interlayer face, it is concrete implements that there is no particular limitation, as long as specific embodiments comprises information described in summary of the invention to the expression of logical record instance data.

User interface aspect for above data means, below provides a kind of embodiment.

Mean known, a definite logical record example of content with " record class name: logical record instance name constant ", as ClassA:ID230871; With " record class name: logical record instance name variable " denoting contents the unknown, probabilistic record instance, as ClassA:X; With " record class name: logical record instance name constant. field name " mean the field of the logical record example that certain content is known, definite, as ClassA:ID230871.name; With " record class name: logical record instance name variable. field name " mean that certain content is unknown, the field of uncertain record instance, as ClassA:X.name.

Field and the available following mode of the relation between constant value for the variable record instance mean:

Record class name: logical record instance name constant. field name r constant value,

Wherein, r means numerical relation, as (being greater than) ,=(being more than or equal to) ,=(equaling) etc.

For the available following mode of the field relation between two record instances, mean:

Recording class name: logical record instance name variable. field name r records class name: logical record instance name constant. field name,

Perhaps,

Recording class name: logical record instance name variable. field name r records class name: logical record instance name variable. field name,

Wherein, r ditto means numerical relation.

For the naming relationship of logical record example, available following mode means:

Record class name: logical record instance name variable R records class name: logical record instance name constant,

Perhaps,

Record class name: logical record instance name variable R records class name: logical record instance name variable,

Wherein, R means the title of relation, as " laboratory test report is arranged ".

For the querying condition meaned by the relation that records, can mean by following mode:

C1?AND?C2?AND?…?AND?Cn，

Wherein, the AND presentation logic " with ", C1, C2 ... Cn is the variable logical record example that means by aforementioned manner and the relation between constant value, or the field relation between two logical record examples, or the naming relationship of logical record example.

For the naming relationship definition rule, can mean by following mode:

IF?C1?AND?C2?AND?…?AND?Cn

THEN records class name: logical record instance name variable R records class name: logical record instance name variable,

Perhaps,

IF?C1?AND?C2?AND?…?AND?Cn

THEN records class name: logical record instance name variable R records class name: logical record instance name constant,

Wherein, R is the name that concerns that will define, the AND presentation logic " with ", C1, C2 ... Cn is the variable logical record example that means by aforementioned manner and the relation between constant value, field relation between perhaps between two logical record examples, or the naming relationship of logical record example.

The embodiment that a kind of count value that middle title variograph is counted to object joins the variable name of the title variable of replacing extra, the middle variable logical record example in the rule condition relation of introducing in expansion process is: general _ xxx_ joins in the variable name of title variable of variable logical record example of described extra, centre as title prefix prefix, and wherein xxx is word string value corresponding to described count value.If adopt this mode that adds, the user when carrying out record queries input as querying condition record relation in the variable name of title variable of variable logical record example can not be with the beginning of this quasiprefix.

Below illustrate the application of processing scheme of variable name of the title variable of this naming relationship definition rule and extra, middle variable logical record example.

Suppose to have following naming relationship definition rule:

IF?Class1:?X.a?=?Class2:?Y.b?AND?Class2:?Y?R1?Class3:?Z

THEN?Class1:?X?R?Class3:?Z;

Suppose that certain records in relation the factor of relation is arranged: Class1:U R Class2:V, the relation that records is launched after subprocess concerns that to this factor is once replaced, launched, obtain to record relation as follows:

Class1:?U.a?=?Class2:?_xxx_Y.b?AND?Class2:?_xxx_Y?R1?Class3:?V，

Here, U, V have substituted respectively title variable X, the Z of the correspondence in the rule condition relation; Xxx is the word string value that middle title variograph is counted the count value of object.Certainly, recording relation expansion subprocess need to further substitute, launch substituting the naming relationship Class2:_xxx_Y R1 Class3:V introduced in expansion process.

The definition rule that limits class for the logical record record can mean by following mode:

IF?C1?AND?C2?AND?…?AND?Cn

The former class name that records of THEN: logical record instance name variable i sOfSameClassAs record limits class name: ANY,

Wherein, ANY is special title variable, means any record instance, and isOfSameClassAs means the relation that records of being scheduled to: belong to the same class that records.

After above restriction class definition has been arranged, the every record in relation occurs: record limits class name: logical record instance name constant, place, all use carrying out when relation is launched: the former class name that records: logical record instance name constant substitutes; Every record records in relation and occurs: record limits class name: variable logical record instance name variable, place, all use: the former class name that records: variable logical record instance name variable, substitute, and add the conditional relationship of corresponding restriction class definition rule in querying condition: AND C1 AND C2 AND ... AND Cn.

Below illustrate the application of this restriction class.

Suppose to have following restriction class definition rule:

IF?Class1:?X.a?>20?AND?Class1:?X?R?Class3:ZZZ

THEN?Class1:?X?isOfSameClassAs?SubClass1:?ANY，

Here ZZZ is the title constant;

Suppose that certain records in relation the factor of relation is arranged: SubClass1:U.b=" Zhang Shan ", the relation that records is launched after subprocess concerns that to this factor is once replaced, launched, obtain to record relation as follows:

Class1:?U.b?=?“Male”?AND?Class1:?U.a?>20?AND?Class1:?U?R?Class3:ZZZ，

Here, U has substituted and has limited the corresponding title variable X in the rule-like conditional relationship.

For the ease of processing, in the specific implementation, being illustrated in system processing aspect for the data that record restriction class and record instance thereof can mean that it is a record restriction class or restriction class record instance with certain special sign, and points to, quotes its former class that records by corresponding data message.

The user interface layer of the above Various types of data means scheme, it is a kind of optional method, in concrete enforcement, the user interface layer form of expression of these data can be considered in conjunction with the data representation schemes synthesis in user's use habit, convenience, data representation ability and system presentation layer, design, as long as can meet described in summary of the invention, requires and provide the relevant information content.

The concrete enforcement that has had above Various types of data to mean, the logical record definition can pass through to select applicable development of information system technology (as ASP.NET, J2EE, C/C++ etc.) with the concrete enforcement that map component S1, naming relationship and restriction class definition assembly S2, logical record enquiring component S3, record launch subprocess S4, and realizes by corresponding flow process.Fig. 2 is the reference flow sheet that the logical record enquiring component is realized, Fig. 3 A-Fig. 3 B records relation to launch the reference flow sheet that subprocess is realized.

The content be not described in detail in this instructions belongs to the known prior art of professional and technical personnel in the field.

Claims

1. the data-base recording data query system based on recording logical expressions, described record logical expressions be a kind of information content comprised with record relevant and with the concrete file layout of record data, mode and location-independent a kind of record data representation or expression way, the record meaned by this form or mode is called logical record; In logical record, a record that comprises concrete data is called the logical record example, is called for short record instance; Be called a logical record class for same purpose, set with logical record example of same alike result; Physical record data corresponding with logical record, that be kept in database are called physical record; The set of recording the record instance that meets certain qualified relation in the record instance set of class forms a new class that records, and is called the former restriction class that records class, or record limits class or restriction and records class or be called for short and limit class;

Described system comprises logical record definition and map component, naming relationship and restriction class definition assembly, logical record enquiring component, the relation that records is launched subprocess and database of record, wherein:

Naming relationship and restriction class definition assembly: a functional module with human-computer interaction interface, domestic consumer records the naming relationship definition rule by this assembly input logic, the definition record naming relationship, and by the restriction class of the existing logical record class of this component definition; Described naming relationship is the denominative relation that records of tool;

The logical record enquiring component: a functional module with human-computer interaction interface, the record queries condition that domestic consumer means by the logical record relation by this assembly input, inquire about, obtain the logical record data that satisfy condition; Described logical record relation is called for short the relation that records;

2. the data-base recording data query system based on recording logical expressions according to claim 1 is characterized in that:

Described logical record definition and map component define the corresponding relation between logical record and logical record data and database physical record data as follows:

The 1st step: define a logical record class and unique name and/or sign;

The 2nd step: define record field that the record instance of described logical record class comprises and the type of each field;

The 5th step: the interrelational form between definition Relational database table;

Different logical record classes and the corresponding database table of record instance thereof and data sheet field both can be identical, also can be different; Described logical record example has one in affiliated title unique in recording class or sign, to represent oneself; The logical record example by the value of certain record field in its record data as its title or sign, or by the derivation value of record field as its title or sign; For a definite or known logical record example, its title is a definite constant be comprised of word string, be called logical record instance name constant or constant title or definite title, corresponding logical record example is called constant logical record example, in the record queries condition, logical record instance name constant represents this determine, known logical record example; For logical record example uncertain or undetermined, its title is a non-quantitative, the interior perhaps value that is title is uncertain, with a variable name, replace, be called logical record instance name variable, corresponding logical record example is called variable logical record example, and when carrying out the record data inquiry, logical record instance name variable represents needs obtain, the one or more logical record examples that meet querying condition of inquiry.

3. the data-base recording data query system based on recording logical expressions according to claim 1 and 2 is characterized in that:

Relation between the described record field that records relation or logical record example and constant value, or the field relation between two logical record examples, or the naming relationship between two logical record examples, or the logic "and" operation of these relations combination; Wherein, relation between the record field of described logical record example and constant value, be the numerical relation between record field and constant value, comprise following information in its expression formula: the title that records class name, logical record example of logical record example, the relevant field name of logical record example and the numerical relation between this field and constant value; Field relation between described two logical record examples, i.e. numerical relation between the record field of two logical record examples, comprise following information in its expression formula: the title that records class name, interrelated logic record instance of interrelated logic record instance, the relevant field name of interrelated logic record instance, and the numerical relation between the record field of interrelated logic record instance; Field relation between the record field of logical record example and constant value between relation and two logical record examples is referred to as logical record instance field relation; Naming relationship between two logical record examples, the relation between two record instances that mean with naming relationship, its expression formula comprises following information: the interrelated logic record instance record class name, the title of interrelated logic record instance, and the title of naming relationship between the interrelated logic record instance; Appear at logical record example or constant logical record example in the relation of record, or variable logical record example; If the logical record example appeared in the relation of record is constant logical record example, its title is used the title constant; If the logical record example appeared in the relation of record is variable logical record example, its title is used the title variable; In recording relational expression, by corresponding mode, distinguish title constant and title variable; Each composing factor in described logical operation combination of recording relation, be the naming relationship between the field relation between relation or two record instances or two record instances between the record field of variable logical record example and constant value, be called the factor that concerns that records relational expression; Describedly concern that the logic evaluation value of the factor is "true" or "false".

4. the data-base recording data query system based on recording logical expressions according to claim 1 and 2 is characterized in that:

Described naming relationship and restriction class definition assembly are used the naming relationship between following naming relationship definition rule definition logical record example:

If two logical record examples also meet the given relation that records by relevant intermediate logic record instance, there is defined naming relationship between these two logical record examples so;

If statement in described contextual definition rule is corresponding to rule condition, and result is set up needs satisfied prerequisite; Statement so in described contextual definition rule is corresponding to regular result, the naming relationship that will define; Two logical record examples that occur in the condition of described rule the given relation that records that need to meet by relevant intermediate logic record instance are called the conditional relationship of naming relationship definition rule, are called for short the rule condition relation; At least one is variable logical record example for two logical record examples in the result of described naming relationship definition rule; Intermediate logic record instance in the conditional relationship of described naming relationship definition rule, refer to occur in the rule condition relation and in rules results absent variable constant or variable logical record example; Recording the title variable of the logical record example occurred in the contextual definition rule, comprise title variable extra, the intermediate variable record instance, is inessential for the definition of recording relation and expression; Can use other defined naming relationships in the conditional relationship of the definition rule of a naming relationship, but the naming relationship itself that directly or indirectly service regeulations will define, can not recursive definition; A naming relationship can define with many described naming relationship definition rules, between many rules, is the relation of logical "or",, as long as a rule is satisfied, between two record instances, has corresponding naming relationship.

5. the data-base recording data query system based on recording logical expressions according to claim 1 and 2 is characterized in that:

Wherein, the given relation that records is the qualified relation to record instance in described logical record class; Described record limits the variable logical record case representation with special title variable variable name for any record instance of class; The title variable of the variable logical record example of any record instance of described expression does not appear in the expression formula of rule condition relation; Based on the described naming relationship definition rule that records especially, allly meet this and belong to same and record the corresponding record instance of variable record instance that class records relation and formed the already present restriction class that records class that will define; Limiting class definition can be nested, in defined restriction, records on the basis of class further definition record and limits class; But limiting class definition can not recurrence, in the rule condition of definition rule, can not comprise directly or indirectly the restriction class itself that will define;

Described special contextual definition rule, only used in naming relationship and restriction class definition component internal; In naming relationship and restriction class definition assembly outside, it is user interface layer, directly do not use, the user only need input following information by special interface when definition record limits class: former class name, the restriction class name that define that records class of the definition class, mean former record class in title variable and the satisfied given relation that records of needs thereof of variable logical record example.

6. the data-base recording data query system based on recording logical expressions according to claim 1 is characterized in that:

Described logical record enquiring component is according to recording record queries condition query that relation means, obtaining the record that required record comprises separately or exist incidence relation, i.e. inquiry obtain with variable logical record example representative, can make the described relation establishment of recording, all logical record examples that the result that makes the logical combination computing of the relation of record is "True";

Step I: by calling one, record naming relationship or the expansion of record restriction class record instance expression formula that relation expansion subprocess will mean that recording of record queries condition comprises in relation, obtain the set of relations that records of an expansion, each in set of relations is all the described formed relation that records of logic "and" operation combination that concerns the factor that the field relation by the logical record example of non-limiting class means, record the field relation between the record field that concerns the factor or variable logical record example of relation and the relation between constant value or two logical record examples, and concern in the factor and do not exist record to limit the logical record example that class means,

7. the data-base recording data query system based on recording logical expressions according to claim 6 is characterized in that:

Input parameter:

1) the to be launched relation that records;

2) in the middle of, the title variograph is counted object, a data object that comprises the integer count value, word string value corresponding to this count value is added into to record and concerns in introduce in expansion process extra, title variable intermediate variable logical record example, to distinguish different middle title variablees or intermediate variable logical record example;

Output parameter:

That 1) has launched records set of relations, by input after the relation that records of launching is launched, obtain suitable, comprise a plurality of set of relationship that record that record relation;

Step 1: each record in relation to be launched of scanning input concerns the factor successively, once surface sweeping runs into one, means with naming relationship or comprise that record limits the factor that concerns of class record instance, proceeds to step 2; Do not run into if scanned with naming relationship and mean or comprise the factor that concerns that record limits the class record instance, the to be launched relation that records that directly will input joins recording in set of relations that output parameter launched, then returns results;

Step 6: call the relation that records and launch subprocess self, it is recursive call self, it is that of taking out from interim, intermediate record set of relations in step 5 records relation that input parameter while calling record to be launched closes, and in the middle of input parameter, the title variograph is counted the middle title variograph that object is current implementation and counted object;

Step 7: to calling the relation that records in step 6, launch the set of relations that records that output parameter that subprocess returns launches and be handled as follows: non-name relation table scanned in current implementation step 1 is shown or do not comprise each in set of relations of recording that limit the class record instance all concern the factor and the expansion of returning and record relation and merges and form the accordingly new relation that records by logic "and" operation, and the new relation that records after all merging is joined to recording in set of relations that the output parameter of current implementation launched;

If the need that scan in described step 1 are to be processed concern the factor be one with naming relationship, mean concern the factor simultaneously and one comprise the factor that concerns that record limits the class record instance, what in described step 2, only by naming relationship, mean concerns factor treatment;

In the described relation that records, launch during subprocess launches to record the process of relation, for determining that its logic evaluation value is the factor that concerns of "True", the replacement of use logical value "True"; For comprising the relation that records that concerns the factor that the logic evaluation value is " vacation ", directly use logical value " vacation " to replace;

Described logical record enquiring component calls described when recording relation and launching subprocess at step I, the relation that records that input parameter is to be launched is the relation that records as the record queries condition, and the count value that the middle title variograph of input parameter is counted object is predetermined initial value; Described, record during relation launches the recursive call process of subprocess, in the middle of the input parameter of transmission title variograph number to as if same data object.

8. the data-base recording data query system based on recording logical expressions according to claim 7 is characterized in that:

9. the data-base recording data query system based on recording logical expressions according to claim 7 is characterized in that:

If there is the logical "or" computing that concerns the factor in to be launched recording in relation, the relation that this recorded is decomposed into a plurality of relations that record that do not comprise the logical "or" computing;

Recorded if to launch in relation and have the logic NOT operation for the logic evaluation value of logical record instance field relation, by this logic NOT operation institute for logical record instance field relation alternative by the logical record instance field relation that does not comprise the NOT operation logical operator of equivalence together with the NOT operation logical operator;

10. according to the described data-base recording data query system based on recording logical expressions of claim 1 or 6, it is characterized in that:

Described logical record enquiring component is set according to corresponding inquiry name, not only the corresponding all logical record examples of variable logical record example that making the relation that records set up are returned in inquiry, and return and make the relation of record set up required all intermediate logic record instances.