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

Database record data query system based on record logic representation

Technical Field

The invention belongs to the technical field of electronic records and databases, and particularly relates to a database record data query system based on record logic representation.

Background

Relational databases are widely used to store various application data. A relational database consists of one or more database tables (database tables) consisting of rows (array) consisting of fields or columns (columns), the application data being finally stored in the corresponding fields of the corresponding row(s) of the database table(s). The data stored in a database table is also called a record (record). Data records stored in different database tables may be associated in some manner to form a larger data record, or to form records having an association relationship, where the former corresponds to the case where one record is stored in multiple different tables, and the latter corresponds to the case where an association relationship exists between different data records (e.g., an association relationship between an electronic medical record of a patient and an electronic laboratory sheet record thereof). The association relationship between records of the same or different kinds is called a record relationship.

The Query of the relational database system for the recorded data which is stored in the database and meets certain conditions or relations adopts an SQL (structured Query language) statement, and the Query of the data record by using the SQL statement has the following limitations or disadvantages:

1) the database table and the fields thereof are required to be directly used for inquiry, the structure of the database table is required to be known, and the method is not suitable for the common people

SQL uses database tables directly, the fields of the tables to represent query conditions, and uses the interrelations (e.g., >, <, = etc.) between the fields of the tables directly to represent the relationships between data records; when record data is stored in multiple different database tables, it is necessary to join (join) the database tables together to query and combine the results of the queries from the different database tables (i.e., integrate the results of the queries for the record fields of the different database tables). The user needs to know the structure of the database table when using the record query condition, the expression mode of the record relation and the combination mode of the query result, and the record query condition, the expression mode of the record relation and the combination mode are only suitable for professional technicians familiar with database technology and having related professional knowledge, and common users cannot use the record query condition, the expression mode of the record relation and the combination mode of the query result at all. In fact, for the general population, they are often concerned with the record data (called logical record) represented in a logical level or an abstract level, such as the name, age, work unit and other information of a certain person, and they are not concerned with the specific storage form of the record data in the database (the specific record data in the database); ordinary users using record data, when expressing records that satisfy certain conditions or relationships, often express the relevant conditions (e.g., identity information of people older than 20 years, identity information of people with the same parents) with record information (data) at a logical level or an abstract level, rather than with specific records in a database table (because they do not even know what is the database at all!).

2) The query can only be carried out aiming at the fixed recorded data content through a human-computer interface, and the flexibility is lacked

Because SQL is not suitable for common users, common users can only query fixed recorded data contents in a given mode through a special human-computer interaction interface provided by a data application system, cannot self-define query objects and query modes according to own needs, and lack flexibility.

3) Records that are not related to each other cannot be queried by naming relationships (namerelationships)

Based on the SQL statement, the relationship between records (two or more) can be represented only by the numerical relationship between the record fields of the database table, and the records satisfying the given relationship are queried and obtained, such as the combination of the record data in a and the record data in B satisfying the equal value of the field a in table 1 and the field B in table 2 in tables 1 and 2, or the associated records from tables 1 and 2 satisfying this relationship, the relationship between records cannot be represented by intuitive relationship names, and the records satisfying this relationship are queried and obtained, such as the combination of electronic records satisfying the "same person" relationship in electronic medical record records and blood drawing laboratory test reports, etc.

The present invention is directed to solving the above problems. The logic representation is a basic mode of knowledge representation, complex knowledge can be represented on the basis, logic reasoning can be carried out, the scheme of the invention borrows some ideas of knowledge representation, such as relation definition through rules, but the logic representation adopted by the invention is different from the common logic representation (namely knowledge representation) theory and method and mainly comprises the following points:

1) the data records in the database are not description information of the knowledge object, but the data records are taken as the knowledge object, and each data field of the recorded data is the description information of the data field;

2) the relation between the specific examples of different knowledge objects is not stored in the database as knowledge;

3) the related knowledge objects (record classes and examples thereof) are not predetermined and fixed, but are defined by the database user according to the need;

4) the data in the relational database has no special requirements on format and storage mode, is suitable for the data of the general relational database, and the application data stored in the relational database does not need to be changed for using the method and the system.

5) Finally, in terms of technical implementation, the technical scheme of the invention does not use a logic representation/knowledge representation complex technology (such as Web Ontology/Resource Description Framework, OWL/RDF) and does not use a related technical tool (such as an OWL/RDF tool); but the query and search of the record data (knowledge) are realized through a simple record relation definition and expansion process and the mapping between the abstract record data and the database record data.

Disclosure of Invention

The purpose of the invention is: the database record data query system based on record logic representation is provided, wherein a user of a database data record can customize abstract classification of database data record objects according to application requirements, and a common user can customize record relations through a human-computer interface, wherein the record relations comprise naming relations which are used as record query conditions to query data required to be recorded without being concerned about specific storage forms and modes of the record data in a database, and the naming relations are record relations with names.

In order to achieve the purpose, the invention adopts the technical scheme that:

a database record data query system based on record logic representation, the record logic representation is a record data representation form or expression form only related to the information content contained in the record and not related to the specific storage form, mode and position of the record data, and the record represented by the form or expression form is called logic record; in the logical record, a record containing specific data is called a logical record instance, which is called a record instance for short; a collection of logical record instances having the same attributes for the same purpose is called a logical record class; specific record data corresponding to the logical record and stored in the database is called a specific record; the collection (subset) of record instances satisfying a certain restricted relationship in the record instance collection of record classes constitutes a new record class, which is called the restricted class of the original record class, or the record restricted class or the restricted record class or the restricted class for short (unless otherwise specified, the record class, record instance, and record relationship refer to a logical record class, a logical record instance, and a logical record relationship hereinafter).

The system comprises a logic record definition and mapping component, a naming relationship and definition class definition component, a logic record query component, a record relationship expansion subprocess and a record database, wherein:

logical record definition and mapping component: a functional module with a human-computer interaction interface, through which a data administrator abstracts the recorded data stored in the relational database, defines a corresponding logical record class, and a corresponding relationship or mapping relationship between the logical recorded data and the database data;

named relationship and defined class definition component: a functional module with a human-computer interaction interface, wherein a common user inputs a logic record naming relationship definition rule through the component, defines a record naming relationship, and defines a definition class of an existing logic record class through the component;

a logical record query component: a functional module with a human-computer interaction interface, wherein a common user inputs a record query condition represented by a logical record relation through the module, and queries and acquires logical record data meeting the condition;

record relationship expansion subprocess: the record data query process is called by a logic record query component, and based on a logic record naming relationship definition rule or a definition class definition rule, the naming relationship and/or the record definition class in the record relationship expression are expanded and replaced, so that the final record relationship expression serving as the record query condition does not contain the naming relationship and/or the record definition class;

a record database: and the relational database system stores specific record data.

The logic record definition and mapping component defines the logic record and the corresponding relation between the logic record data and the specific record data of the database according to the following steps:

step 1: defining a logical record class and its unique name and/or Identification (ID);

step 2: defining record fields and the type of each field (such as string, text, byte, integer, date, time, etc.) contained by the record instance of the logical record class;

and 3, step 3: defining the corresponding relation between the logic record class and the database table, wherein the corresponding relation comprises the names of one or more database tables corresponding to the logic record class;

and 4, step 4: defining a corresponding relation or a mapping relation between a record field of a record instance of the logic record class and a field of the corresponding database table;

and 5, step 5: the manner of association between related database tables is defined (e.g., by which fields of the database tables are associated with each other).

The database tables and the data table fields corresponding to different logic record classes and record instances thereof can be the same or different; the logic record instance has a unique name or identification in the belonged record class to represent itself; a logical record instance may use a value of a record field (e.g., a name, an identity number of a corresponding record body) in its record data as its name or identifier, or use a derived value of a record field as its name or identifier; for a certain or known logic record instance, the name of the certain or known logic record instance is a certain constant composed of strings and is called as a logic record instance name constant (or constant name, certain name), the corresponding logic record instance is called as a constant logic record instance, and in the record query condition, the logic record instance name constant represents the certain and known logic record instance; for an uncertain or undetermined logical record instance, the name of the uncertain or undetermined logical record instance is an indeterminate quantity (namely, the content or the value of the name is uncertain), a variable name is used for replacing the uncertain or undetermined logical record instance, the name is called a logical record instance name variable, the corresponding logical record instance is called a variable logical record instance, and when record data query is carried out, the logical record instance name variable represents one or more logical record instances which need query acquisition and meet query conditions.

The record relation is either the relation between the record field of the logic record instance and a constant value, or the field relation between two logic record instances, or the naming relation between two logic record instances, or the logical AND operation combination of the relations; wherein, the relation between the record field of the logic record instance and the constant value, namely the numerical relation (such as >, <, =, | =) between the record field and the constant value, the following information is included in the expression: the record class name of the logical record instance, the associated field name of the logical record instance, and the numerical relationship between this field and a constant value (e.g., the value of field a of record instance X of logical record class A equals 123); the field relationship between the two logic record instances, namely the numerical relationship between the record fields of the two logic record instances, includes the following information in the expression: record class names of related logical record instances, related field names of related logical record instances, and numerical relationships between record fields of related logical record instances (e.g., the value of field a of record instance X of logical record class a is equal to the value of field B of record instance Y of logical record class B); the relationship between the record field of a logical record instance and a constant value and the field relationship between two logical record instances are collectively referred to as a logical record instance field relationship; named relationship between two logic record instances, namely, relationship between two record instances represented by the named relationship, the expression of which contains the following information: record class names of the related logical record instances, and names of naming relationships between the related logical record instances; the logic record instance appearing in the record relation is either a constant logic record instance or a variable logic record instance; if the logic record instance appearing in the record relationship is a constant logic record instance, the name thereof uses a name constant; if the logic record instance appearing in the record relationship is a variable logic record instance, the name thereof uses a name variable; in the record relational expression, distinguishing the name constant and the name variable in a corresponding manner (e.g., add a question mark to the variable name of the name variable; each component factor (Element) in the logical operation combination of the record relations, namely the relation between the record field of the variable logical record instance and a constant value or the field relation between two record instances or the named relation between two record instances, is called as a relation factor of the record relational expression; the logical evaluation value of the relationship factor is "true" or "false".

The named relationship and define class definition component defines named relationships between instances of logical records using named relationship definition rules as follows:

if two logical record instances satisfy a given record relationship through an associated intermediate logical record instance, then there is a defined naming relationship between the two logical record instances.

The 'if' statement in the relation definition rule corresponds to a rule condition, namely the result is satisfied and needs to be satisfied; the "then" statement in the relationship definition rule corresponds to the result of the rule, i.e., the named relationship to be defined; the given record relation (namely, the record relation in the 'if') which is required to be satisfied by two logic record instances appearing in the condition of the rule and through the related intermediate logic record instance is called a condition relation (called a rule condition relation for short) of the naming relationship definition rule; at least one of the two logical record instances in the result (i.e., "then") of the named relationship definition rule is a variable logical record instance; the intermediate logical record instance in the conditional relationship of the named relationship definition rule refers to a constant or variable logical record instance that appears in the rule conditional relationship but does not appear in the rule result (e.g., a relationship rule: if the value of field a of record instance X of logical record class a is equal to the value of field B of record instance Y of logical record class B, and the value of field C of record instance Y of record class B is equal to the value of field e of record instance Z of record class C, then there is a relationship R between record instance X of logical record class a and record instance Z of record class C, where Y is the name variable of the additional, intermediate variable logical record instance introduced in defining the relationship between record instance X and record instance Z); the name variables of the logical record instances that appear in the record relationship definition rules, including the name variables of the additional, intermediate variable record instances, are immaterial for the definition and expression of the record relationships; other defined naming relations can be used in the condition relation of the definition rule of one naming relation, but the naming relation to be defined by the rule can not be directly or indirectly used, namely, the naming relation can not be defined recursively; a named relationship may be defined by a plurality of named relationship definition rules, with a logical OR relationship between the rules, i.e., a corresponding named relationship exists between two record instances as long as a rule is satisfied.

The naming relationship and definition component provides the definition function of the record definition class through the following special logic record naming relationship definition rules:

if a variable record instance of an existing logical record class satisfies a given record relationship with other intermediate logical record instances, then this variable logical record instance has a predetermined naming relationship with any instance in the record definition class to be defined: belong to the same record class;

wherein, the given record relation is a defined relation of the record instance in the logic record class; ANY record instance of the record definition class is represented by a logical record instance of a variable with a special name variable (e.g., using the name variable; the name variable (e.g.,; based on the special record naming relationship definition rule, all record instances corresponding to the variable record instances meeting the record relationship of 'belonging to the same record class' form a definition class of the existing record class to be defined; the definition of the definition class can be nested, namely, the definition class of the record is further defined on the basis of the defined definition record class; but the definition of a defined class cannot be recursive, i.e. the defined class itself to be defined cannot be directly or indirectly contained in the rule conditions defining the rule.

The special relationship definition rules described above are used only within the naming relationship and defining class definition components; outside the naming relationship and definition class defining component, namely the user interface layer, the user interface layer is not directly used, and the user only needs to input the following information through a special interface when defining the record definition class: the method comprises the following steps of defining a class name of an original record class of a defined class, defining the class name to be defined, representing a name variable of a variable logic record instance in the original record class and a given record relation required to be satisfied.

The logic record query component queries and acquires required records including records with single or existing association relation according to the record query condition represented by the record relation, namely queries and acquires all logic record instances which are represented by variable logic record instances and can enable the record relation to be established, namely, the result of logic combination operation of the record relation is true.

The logic record query component queries and acquires the required record data according to the record query condition represented by the record relation according to the following steps:

step I: expanding a naming relationship or a record definition class record instance expression contained in a record relationship representing a record query condition by calling a record relationship expansion subprocess (subprogram, function) to obtain an expanded record relationship set, wherein each item in the relationship set is a record relationship formed by the logical and operation combination of relationship factors represented by the field relationship of a logic record instance of an undefined class, namely the relationship factor of the record relationship is the relationship between the record field of a variable logic record instance and a constant value or the field relationship between two logic record instances, and the logic record instance represented by the record definition class does not exist in the relationship factor;

step II: sequentially taking each record relation in the expanded record relation set in the step I as a record query condition to execute the operations from the step III to the step IV, and returning a result after the processing is finished;

step III: according to the corresponding relation or mapping relation between the record data of the logical record and the concrete record data in the database, converting the record relation which only contains the field relation of the logical record and is used as a record query condition into the record query condition expressed by the field of the database table in the database and generating a corresponding SQL statement;

step IV: and querying a database based on the SQL sentences generated by the conversion in the step III, converting specific recorded data results obtained by querying the database into logic recorded data, and merging the obtained logic recorded data into a final query result which needs to be returned.

The record relationship expansion sub-process called by the logical record query component in step I has the following entry parameters:

inputting parameters:

1) record relationships to be expanded;

2) an intermediate name variable counting object, a data object containing an integer counting value, wherein the string value corresponding to the counting value is inserted into the name variable of an additional intermediate variable logic recording example introduced in the record relation expansion process so as to distinguish different intermediate name variables or intermediate variable logic recording examples;

outputting parameters:

1) the expanded record relation set is an equivalent record relation set which is obtained by expanding the input record relation to be expanded and comprises a plurality of record relations.

The record relationship expansion subprocess operates according to the following steps:

step 1: scanning each relation factor in the input record relation to be expanded in sequence, and once the scanning surface encounters a relation factor which is expressed by a named relation or contains a record limiting type record instance, turning to the step 2; if the scanning is finished and the relation factor represented by the naming relation or containing the record instance of the record limit class is not encountered, directly adding the input record relation to be expanded into the record relation set with the expanded output parameters, and then returning the result (the output result only contains one record relation, namely the input record relation to be expanded);

step 2: if the relationship factor to be processed scanned in step 1 is a record relationship between two record instances represented by a naming relationship, the naming relationship is replaced by a conditional relationship of a naming relationship definition rule, otherwise, the relationship factor containing the record instance of the record definition class is processed as follows: firstly, replacing the record limit class of the limit class logic record instance in the relation factor expression by using the corresponding original record class, and then adding the condition relation in the record limit class definition rule into the replaced relation factor through logic AND; in the substitution processing process, the name variable of the related variable logic record instance in the rule condition relation used for substitution is replaced by the name constant or the name variable of the corresponding logic record instance in the relation factor being processed; for the name variable of an additional intermediate variable logic recording example in the rule condition relation introduced in the replacement and expansion process, adding a string value corresponding to the counting value of the intermediate name variable counting object into the variable name of the name variable of the additional intermediate variable logic recording example according to a preset mode; if the naming relationship or the record definition logic record instance to be replaced and expanded corresponds to a plurality of naming relationship definition rules, replacing the naming relationship or the record definition logic record instance with the condition relationship of each relationship definition rule respectively to obtain a plurality of relationship factors after replacement and expansion;

and step 3: combining one or more expanded relation factors obtained after the substitution treatment in the step 2 with the rest relation factors which are not scanned according to logic 'AND' to obtain one or more temporary and intermediate record relations to be expanded; generating a set by all temporary and intermediate record relations to be expanded obtained by the processing;

and 4, step 4: adding 1 to the count value in the intermediate name variable counting object;

and 5: sequentially taking out each record relation in the temporary and middle record relation set to be expanded generated in the step 3, and executing the processing of the step 6-7; returning a result after the processing is finished;

step 6: calling a recording relation expansion subprocess (namely, recursively calling the subprocess), wherein the recording relation to be expanded of the input parameters during calling is a recording relation which is taken out from the temporary and intermediate recording relation set in the step 5, and the intermediate name variable counting object of the input parameters is an intermediate name variable counting object of the current execution process;

and 7: and 6, processing the record relation set expanded by the output parameters returned by the record relation expanding subprocess called in the step 6 as follows: and merging all relation factors which are represented by the scanned non-named relation or do not contain the limit class record instance in the step 1 of the current execution process and each record relation in the returned expanded record relation set according to logical AND operation to form a corresponding new record relation, and adding all the merged new record relations into the expanded record relation set of the output parameter of the current execution process.

If the relationship factor to be processed scanned in step 1 is both a relationship factor represented by a named relationship and a relationship factor containing a record instance of the record definition class, then only the relationship factor represented by the named relationship is processed in step 2.

In the process of expanding the record relationship in the record relationship expanding sub-process, for a relationship factor (such as the field relationship of two constant logic record instances) of which the logic evaluation value is determined to be true, replacing the relationship factor with a logic value of true; for a recorded relationship containing a relationship factor in which the logical evaluation value is "false", the logical value "false" is directly substituted.

When the logic record query component calls the record relationship expansion subprocess in step I, the record relationship to be expanded of the input parameter is the record relationship serving as the record query condition, and the count value of the intermediate name variable counting object of the input parameter is a predetermined initial value (such as 0 or 1). In the recursive calling process of the record relation expansion subprocess, the passed input parameter intermediate name variable counting objects are the same data object (such as the same C/C + + data object pointed to by a data pointer or the same Java object pointed to by an object reference).

The predetermined manner of adding the string value corresponding to the count value of the intermediate name variable counting object to the name variable of the additional and intermediate variable logic recording instance in the rule condition relationship introduced in the replacement deployment process in the step 2 is not particularly specified, as long as the name variable of the additional and intermediate variable logic recording instance introduced in the deployment process is not repeated with the name variables of the other variable logic recording instances.

The record relation expansion subprocess is expanded by the following functions, and allows a logic record query component to generate a logic or and/or not operation combination of relation factors in the record relation to be expanded which is input as a record query condition when the subprocess is called, or in a condition relation of a definition rule of a naming relation:

if the record relation as the query condition has logical OR operation of the relation factor, decomposing the record relation into a plurality of record relations not containing the logical OR operation (then respectively using each record relation obtained by decomposition as the query condition to query and obtain data, and finally merging the query and obtain results);

if a logical not operation of a logical evaluation value aiming at the logical record instance field relation exists in the record relation as the query condition, replacing the logical record instance field relation aiming at the logical not operation and the logical not operation operator by an equivalent logical record instance field relation not containing the logical not operation operator (such as changing the field relation of the record instance to be equal to or not equal to or less than or changing the field relation of the record instance to be equal to or not less than or equal to or not less than) together with the logical not operation operator;

if logic 'OR' operation of the relation factor exists in the rule condition relation serving as the naming relation definition rule, the rule condition relation is decomposed into a plurality of record relations which do not contain the logic 'OR' operation, then each record relation obtained through decomposition is used as the rule condition relation of the naming relation definition rule, and a plurality of naming relation definition rules which are 'OR' relations are obtained;

if the logic 'not' operation of the logic record instance field relation exists in the rule condition relation serving as the naming relation definition rule, the logic record instance field relation and the 'not' operation logic operator which are aimed at by the logic 'not' operation are replaced by the equivalent logic record instance field relation which does not contain the 'not' operation logic operator.

The logic record query component is set according to the corresponding query command, and can query and acquire all logic record instances corresponding to the variable logic record instances enabling the record relationship to be established, and can return all intermediate logic record instances enabling the record relationship to be established.

The innovation of the invention is that: the method is characterized in that some ideas and methods of logic representation are used for querying database record data, and a general method and a system for querying the record data of the relational database based on the record logic representation are provided; the method and the system enable the representation of the record query condition or the command to be used by common users by representing the record query condition by the logic record and defining the corresponding relation between the logic record data and the concrete record data of the database; by introducing the record naming relationship and the record limiting class, the expression of the record query condition is simpler; the method and the system use partial ideas and methods of logic representation, but do not adopt complex technology of logic representation.

Drawings

Fig. 1 is an overall structural view of the present invention.

FIG. 2 is a flow diagram of an implementation of the logical record query component of the present invention.

3A-3B are flow charts of the record relationship expansion sub-process of the present invention.

Detailed Description

The present invention is described in further detail below with reference to the attached drawing figures.

The invention relates to a database record data query method and a database record data query system based on record logic representation, the overall structure of the system is shown in figure 1, a solid arrow represents a use direction, a hollow arrow represents a data generation direction, wherein a logic record definition and mapping component S1, a naming relationship and definition class definition component S2, a logic record query component S3, a record relationship expansion sub-process S4, a database S5 are functional components, and the rest are related data. The functions and functions of the elements in the drawings are discussed in the summary of the invention, and are not repeated here, and the relationship between the elements is described simply as follows:

the data administrator abstracts (T2) the record data (concrete record) S6 in the database S5 by using (T1) the logical record definition and mapping component S1, generates (G1) a logical record S7 (including logical record classes and instances thereof), generates (G2) a mapping relationship S8 between the logical record and the database record; relationship between logical record instance field and constant value S9 uses (T3) logical record S7; the field relationship between two logical record instances S10 uses (T4) logical record S7; the user enters (G3) a naming relationship definition rule S11 using (T5) a naming relationship and defined class definition component S3; the naming relationship definition rule S11 uses (T6, T7, T8) logical record instance field to constant value relationship S9, field relationship S10 between two logical record instances and defined logical record instance naming relationship S12, or defines, generates (G4) new logical record instance naming relationship S12, or defines, generates (G5) defined classes (new record classes) of existing logical record classes; the record relation S13 of the logical record instance is represented by the logical operation combination of (T9, T10, T11) the relation S9 between the logical record instance field and the constant value, the field relation S10 between the two logical record instances and the logical record instance naming relation S12; the user queries the record data by the (T12) logical record query component S3 using (T13) record relationship S13 as a query condition; the logical record query component S3 invokes (T14) the relationship expansion sub-process S4 when querying the record data based on the record relationship; the relation expansion subprocess S4 uses (T15) the record relation definition rule S11, or performs replacement and expansion processing on the named relation in the record relation, or performs replacement and expansion processing on the definition class in the record relation, so that the record relation as the record query condition after replacement and expansion only contains the field relation of the logical record instance; then, the logical record query component S3 converts the record query conditions and names only including the logical record instance field relationship by using (T16) the logical record and concrete record mapping relationship S8, and generates (G5) a database query SQL statement S14; the database query SQL statement S14 is then used to query, retrieve (T18) the specific record data S6 in the database S5, and then present the queried record data to the user in the form of (T19) logical records.

With the above relationship description, the specific implementation of the present invention mainly relates to: the implementation of the representation of various types of data, as well as the logical record definition and mapping component S1, the naming relationship and definition class definition component S2, the logical record query component S3, and the record relationship expansion sub-process S4 are described separately below with respect to their specific implementations.

The various types of data mainly comprise: the method comprises the following steps of defining data by logical records (including record classes and record examples), describing data of corresponding relations between the logical record data (fields of the logical record examples) and database record data (database tables and fields), representing the data by the logical record examples, representing the data by the record relations and representing the data by the record relation definition rules. All these data representations are in two levels: system processing level, user interface level. The data representation of the system processing level refers to a data representation form which is stored in a memory, a file and/or a database and can be processed by a computer system; the data representation of the user interface table layer refers to a data representation form which is seen through a human-computer interaction interface of a computer or written on a paper medium.

The specific implementation of the definition data of the logical record, the description data of the corresponding relationship between the logical record data and the database record data, whether in the system processing level or the user interface level, is not particularly limited as long as the specific implementation can reflect the contents and the expressed information described in tables 1 and 2: table 1 illustrates the content required to define a logical record class, record instance fields, and describe the record field to database table correspondence; table 2 illustrates the content and information required to associate two database tables (User table in database and AddressTable table in database are associated by their fields UID, although the fields in the two tables may be of different names).

TABLE 1 logical record (class, instance) definitions and mapping description with database record data

Table 2 associative relations of database tables

Database table 1	Table 1 associated fields	Database table 2	Table 2 associated fields
				User	UID	AddressTable	UID

Likewise, the specific implementation of the representation of the logical record instance data, whether at the system processing level or the user interface level, is not particularly limited, as long as the specific implementation contains the following information: the record type to which the record instance belongs, the name of the record instance, the included record field and the corresponding data of the field. In the data representation of the logical record instance, it is necessary to distinguish a certain record instance (constant record instance) with known data content from a certain record instance (variable record instance) with unknown content and uncertainty, for example, a flag may be used to represent and distinguish two different logical record instances in a data structure representing the record instance in a memory; in the user interface layer, one can precede the variable name of the name variable of the recording instance.

Similarly, the specific implementation of the record relationship representing data and the record relationship definition rule representing data, whether in the system processing level or the user interface level, is not particularly limited as long as the representation of the logical record instance data by the specific implementation includes the information described in the summary of the invention.

For the user interface level representation of the above data, an embodiment is given below.

The method is characterized in that a definite logic record instance with known content is represented by a record class name, a logic record instance name constant, such as ClassA: ID 230871; is the logical record instance name variable "denoted an uncertain record instance of unknown content, such as ClassA:; the field name represents a field of a certain logic record instance with known and determined content, such as ClassA, ID230871, name; the field name represents a field of a record instance of unknown, uncertain content, such as ClassA.

The relationship between the fields and constant values for a variable record instance can be represented as follows:

record class name,

wherein r represents a numerical relationship, such as > (greater than), > = (greater than or equal to), = (equal to), and the like.

The field relationship between two record instances can be represented as follows:

record class name,

or,

record class name,

wherein r represents a numerical relationship as before.

The named relationship for a logical record instance can be represented as follows:

record class name,

or,

record class name,

wherein R represents the name of the relationship, such as "there is a laboratory test report".

The query condition represented by the record relationship can be represented as follows:

C1 AND C2 AND … AND Cn，

where AND represents logical AND, C1, C2 … Cn are relationships between instances of logical records of variables AND constant values, or field relationships between two instances of logical records, or naming relationships of instances of logical records, represented in the foregoing manner.

The rules may be defined for a named relationship in the following way:

IF C1 AND C2 AND … AND Cn

THEN records the class name,

or,

IF C1 AND C2 AND … AND Cn

THEN records the class name,

where R is the name of the relationship to be defined, AND represents the logical AND, C1, C2 … Cn are the relationships between the variable logical record instances AND the constant values, or the field relationships between two logical record instances, or the naming relationships of the logical record instances, represented in the manner described above.

An embodiment of adding the count value of the intermediate name variable count object to the variable name of the name variable of the additional, intermediate variable logic record instance that replaces the rule-condition relationship introduced during the deployment process is: adding _ xxx _ as a name prefix to the variable name of the name variable of the additional, intermediate instance of the logical record of variables, where xxx is the string value to which the count value corresponds. With this addition method, the variable name of the name variable of the logical record instance of the variable in the record relationship as the query condition input by the user when performing the record query cannot be started with such a prefix.

The following illustrates the application of this naming relationship definition rule and the processing scheme of the variable name of the name variable of the additional, intermediate variable logic record instance.

Assume the following naming relationship definition rules:

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

THEN Class1:?X R Class3:?Z;

let us assume that the relationship factor in a certain record relationship: class1:

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

here, U, V replaces the corresponding name variable X, Z in the rule condition relationship, respectively; xxx is the string value of the count value of the intermediate name variable count object. Of course, the record relationship expansion sub-process requires further substitution, expansion of the named relationship Class 2.

The definition rules for a logical record definition class can be expressed as follows:

IF C1 AND C2 AND … AND Cn

the than original record class name,

where, is ANY special name variable representing ANY record instance, isOfSameClassAs represents a predetermined record relationship: belonging to the same record class.

With the above definition of the defined class, all occurrences in the record relationship are: record the defined class name: where the logic records instance name constants, it uses: original record class name: logic records instance name constants, substitutions; all occurrences in the record relationship: record the defined class name: where the variable logic records the instance name variable, all use: original record class name: the variable logic records the instance name variable, replaces the instance name variable, and adds the corresponding condition relation of the definition rule of the definition class into the query condition: AND C1 AND C2 AND … AND Cn.

The following illustrates the application of this class of restriction.

Assume that the following defined class definition rules are set:

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

THEN Class1:?X isOfSameClassAs SubClass1:?ANY，

where ZZZ is a name constant;

let us assume that the relationship factor in a certain record relationship: SubClass1:

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

here, U replaces the corresponding name variable X in the qualified class rule condition relationship.

For convenience of processing, in implementation, the data representation of the record definition class and the record instance thereof may be represented by a special flag at a system processing level, and the special flag indicates that the record definition class or the record instance of the record definition class is a record definition class or a record instance of the record definition class, and points to and refers to the original record class thereof through corresponding data information.

The user interface layer representation schemes of the various data are only an optional method, and in specific implementation, the user interface layer representation forms of the data can be comprehensively considered and designed by combining the use habits, convenience and data expression capability of users and the data representation schemes in the system representation layer as long as the requirements in the invention content can be met and the related information content can be provided.

With the above implementation of various data representations, the implementation of the logical record definition and mapping component S1, the naming relationship and definition class definition component S2, the logical record query component S3, and the record expansion sub-process S4 can be implemented by selecting a suitable information system development technology (such as asp. net, J2EE, C/C + +, etc.), and by a corresponding process. FIG. 2 is a reference flow diagram for a logical record query component implementation and FIGS. 3A-3B are reference flow diagrams for a record relationship expansion sub-process implementation.

Those not described in detail in this specification are within the skill of the art.

Claims

1. A database record data query system based on record logic representation, the record logic representation is a record data representation form or expression form only related to the information content contained in the record and not related to the specific storage form, mode and position of the record data, and the record represented by the form or expression form is called logic record; in the logical record, a record containing specific data is called a logical record instance, which is called a record instance for short; a collection of logical record instances having the same attributes for the same purpose is called a logical record class; specific record data corresponding to the logical record and stored in the database is called a specific record; the collection of the record instances satisfying a certain limit relation in the record instance collection of the record class forms a new record class, which is called the limit class of the original record class, or the record limit class or the limit record class or the limit class for short;

named relationship and defined class definition component: a functional module with a human-computer interaction interface, wherein a common user inputs a logic record naming relationship definition rule through the component, defines a record naming relationship, and defines a definition class of an existing logic record class through the component; the named relation is a record relation with a name;

a logical record query component: a functional module with a human-computer interaction interface, wherein a common user inputs a record query condition represented by a logical record relation through the module, and queries and acquires logical record data meeting the condition; the logical record relationship is called record relationship for short;

2. The system of claim 1, wherein the database record data query system based on record logic representation comprises:

the logic record definition and mapping component defines the logic record and the corresponding relation between the logic record data and the concrete record data of the database according to the following steps:

step 1: defining a logical record class and its unique name and/or identification;

step 2: defining record fields contained by record instances of the logical record class and the type of each field;

and 5, step 5: defining an association mode between related database tables;

the database tables and the database fields corresponding to different logic record classes and record instances thereof can be the same or different; the logic record instance has a unique name or identification in the belonged record class to represent itself; the logical record instance uses the value of a record field in the record data as the name or identification thereof, or uses the derived value of the record field as the name or identification thereof; for a certain or known logic record instance, the name of the certain or known logic record instance is a certain constant composed of strings and is called as a logic record instance name constant or a constant name or a certain name, the corresponding logic record instance is called as a constant logic record instance, and in the record query condition, the logic record instance name constant represents the certain and known logic record instance; for an uncertain or undetermined logical record instance, the name of the uncertain or undetermined logical record instance is an indeterminate quantity, namely, the content or the value of the name is uncertain, a variable name is used for replacing the uncertain or undetermined logical record instance, the name is called a logical record instance name variable, the corresponding logical record instance is called a variable logical record instance, and when record data query is carried out, the logical record instance name variable represents one or more logical record instances which need query acquisition and meet query conditions.

3. The system according to claim 1 or 2, wherein:

the record relation is either the relation between the record field of the logic record instance and a constant value, or the field relation between two logic record instances, or the naming relation between two logic record instances, or the logical AND operation combination of the relations; the relation between the record field of the logic record instance and the constant value, namely the numerical relation between the record field and the constant value, includes the following information in the expression: the record class name of the logic record instance, the related field name of the logic record instance and the numerical relation between the field and the constant value; the field relationship between the two logic record instances, namely the numerical relationship between the record fields of the two logic record instances, includes the following information in the expression: the record class name of the relevant logic record instance, the relevant field name of the relevant logic record instance, and the numerical relationship among the record fields of the relevant logic record instance; the relationship between the record field of a logical record instance and a constant value and the field relationship between two logical record instances are collectively referred to as a logical record instance field relationship; named relationship between two logic record instances, namely, relationship between two record instances represented by the named relationship, the expression of which contains the following information: record class names of the related logical record instances, and names of naming relationships between the related logical record instances; the logic record instance appearing in the record relation is either a constant logic record instance or a variable logic record instance; if the logic record instance appearing in the record relationship is a constant logic record instance, the name thereof uses a name constant; if the logic record instance appearing in the record relationship is a variable logic record instance, the name thereof uses a name variable; in the recording relational expression, distinguishing a name constant and a name variable in a corresponding mode; each component factor in the logical operation combination of the record relationship, namely the relationship between the record field of the variable logical record instance and a constant value or the field relationship between two record instances or the naming relationship between two record instances, is called as a relationship factor of the record relational expression; the logical evaluation value of the relationship factor is "true" or "false".

4. The system according to claim 1 or 2, wherein:

the named relationship and defined class definition component defines named relationships between instances of logical records using named relationship definition rules as follows:

if two logical record instances satisfy a given record relationship through an associated intermediate logical record instance, then there is a defined naming relationship between the two logical record instances;

if the statement in the relation definition rule corresponds to the rule condition, the result is satisfied and needs to be satisfied; then statements in the relationship definition rule correspond to the result of the rule, i.e. the named relationship to be defined; the given record relation which is formed by two logic record instances appearing in the condition of the rule and needs to be met through the related middle logic record instance is called a condition relation of a naming relation definition rule, and is called a rule condition relation for short; at least one of the two logical record instances in the result of the named relationship definition rule is a variable logical record instance; the intermediate logic record instance in the condition relation of the named relation definition rule refers to a constant or variable logic record instance which appears in the rule condition relation but does not appear in the rule result; the name variables of the logical record instances that appear in the record relationship definition rules, including the name variables of the additional, intermediate variable record instances, are immaterial for the definition and expression of the record relationships; other defined naming relations can be used in the condition relation of the definition rule of one naming relation, but the naming relation to be defined by the rule can not be directly or indirectly used, namely, the naming relation can not be defined recursively; a named relationship may be defined by a plurality of named relationship definition rules, with a logical OR relationship between the rules, i.e., a corresponding named relationship exists between two record instances as long as a rule is satisfied.

5. The system according to claim 1 or 2, wherein:

wherein, the given record relation is a defined relation of the record instance in the logic record class; any record instance of the record definition class is represented by a variable logic record instance with a special name variable name; the name variable of the variable logic record instance representing any record instance does not appear in the expression of the rule condition relation; based on the special record naming relationship definition rule, all record instances corresponding to the variable record instances meeting the record relationship of the same record class form a defined class of the existing record class to be defined; the definition of the definition class can be nested, namely, the definition class of the record is further defined on the basis of the defined definition record class; but the definition of the definition class cannot be recursive, i.e. the definition class itself to be defined cannot be directly or indirectly contained in the rule condition of the definition rule;

the special relation definition rule is only used in the naming relation and definition component of the definition class; outside the naming relationship and definition class defining component, namely the user interface layer, the user interface layer is not directly used, and the user only needs to input the following information through a special interface when defining the record definition class: the method comprises the following steps of defining a class name of an original record class of a defined class, defining the class name to be defined, representing a name variable of a variable logic record instance in the original record class and a given record relation required to be satisfied.

6. The system of claim 1, wherein the database record data query system based on record logic representation comprises:

the logic record query component queries and acquires required records including records with single or existing association relation according to the record query condition represented by the record relation, namely queries and acquires all logic record instances which are represented by variable logic record instances and can enable the record relation to be established, namely, all logic record instances which enable the result of logic combination operation of the record relation to be true;

step I: expanding a naming relationship or record limited class record instance expression contained in a record relationship representing a record query condition by calling a record relationship expansion subprocess to obtain an expanded record relationship set, wherein each item in the relationship set is a record relationship formed by the logical and operation combination of the relationship factors represented by the field relationship of the logical record instance of the non-limited class, namely the relationship factor of the record relationship is the relationship between the record field of the record instance of the variable logical record instance and a constant value or the field relationship between two logical record instances, and the logical record instance represented by the record limited class does not exist in the relationship factor;

7. The system of claim 6, wherein the database record data query system based on record logic representation comprises:

inputting parameters:

1) record relationships to be expanded;

2) the intermediate name variable counting object is a data object containing an integer counting value, and the string value corresponding to the counting value is added into the name variable of an additional intermediate variable logic recording example introduced in the record relation expansion process so as to distinguish different intermediate name variables or intermediate variable logic recording examples;

outputting parameters:

1) the expanded record relation set expands the input record relation to be expanded to obtain an equivalent record relation set which comprises a plurality of record relations;

step 1: scanning each relation factor in the input record relation to be expanded in sequence, and once the scanning surface encounters a relation factor which is expressed by a named relation or contains a record limiting type record instance, turning to the step 2; if the relation factor represented by the named relation or containing the record limiting type record instance is not encountered after the scanning is finished, directly adding the input record relation to be expanded into the record relation set with the expanded output parameters, and then returning the result;

step 6: calling a recording relation expansion subprocess, namely recursively calling the subprocess, wherein the recording relation to be expanded of the input parameters during calling is a recording relation which is taken out from the temporary and intermediate recording relation set in the step 5, and the intermediate name variable counting object of the input parameters is an intermediate name variable counting object of the current execution process;

and 7: and 6, processing the record relation set expanded by the output parameters returned by the record relation expanding subprocess called in the step 6 as follows: merging all relation factors which are represented by the scanned non-naming relation or do not contain the limit class record instance in the step 1 of the current execution process and each record relation in the returned expanded record relation set according to logical AND operation to form a corresponding new record relation, and adding all the merged new record relations into the expanded record relation set of the output parameters of the current execution process;

if the relationship factor to be processed scanned in the step 1 is both a relationship factor represented by a named relationship and a relationship factor containing a record instance of the record definition class, processing the relationship factor represented by the named relationship only in the step 2;

in the process of developing the record relationship in the record relationship development subprocess, replacing a relationship factor for which the logical evaluation value can be determined to be true with a logical value true; for the record relationship containing the relationship factor of which the logic evaluation value is false, directly replacing the record relationship with the logic value false;

when the logic record query component calls the record relationship expansion subprocess in the step I, the record relationship to be expanded of the input parameter is the record relationship serving as a record query condition, and the count value of the variable counting object of the intermediate name of the input parameter is a preset initial value; and in the recursive calling process of the record relation expansion subprocess, the transferred intermediate name variable counting objects of the input parameters are the same data object.

8. The system of claim 7, wherein the database record data query system based on record logic representation comprises:

9. The system of claim 7, wherein the database record data query system based on record logic representation comprises:

if the logical OR operation of the relation factor exists in the record relation to be expanded, decomposing the record relation into a plurality of record relations which do not contain the logical OR operation;

if the record relation to be expanded has logical 'not' operation aiming at the logical evaluation value of the logical record instance field relation, replacing the logical record instance field relation and the 'not' operation logical operator which are aimed at by the logical 'not' operation with the equivalent logical record instance field relation which does not contain the 'not' operation logical operator;

10. The system according to claim 1 or 6, wherein:

the logic record query component is set according to the corresponding query name, and not only queries and returns all logic record instances corresponding to the variable logic record instances enabling the record relationship to be established, but also returns all intermediate logic record instances required for enabling the record relationship to be established.