JPH06348569A - Data base system - Google Patents

Abstract

PURPOSE:To make display and input operation easy to understand and reduce required capacity by storing records as code data and performing conversion between the code data and character data by the correspondence between the both. CONSTITUTION:A data base main body 10 codes records in fields of smaller than specific size in a set of records 100 consisting of fields 1000 including character data and code data as elements and stores the results as code data, and also stores a code correspondence character string 300 which shows the correspondence between the code data and character data. A retrieval part 40 searches the code correspondence character string 300 for a character string of a field 1000 in a record 100 and performs mutual conversion from a code to a character string or vice versa and a display and print part 30 displays and prints the character string in the code correspondence character string 300 corresponding to the code of the field 1000 in the record 100 searched for by the retrieval part 40.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database system having character data (character string information) as a record element.

[0002]

2. Description of the Related Art In a conventional database system, a record containing character data has character data for each record of the data. That is, the same character string is stored in each record even if the same character string is likely to be entered. For example, when a specific company name appears as character data in a plurality of records in a company name field of a customer list, a model name of the specific company appears in a plurality of records as a character data in a field of a handling model. Also, if the company name, model name, etc. are defined as code (numerical) fields from the beginning, data will be saved, but the correspondence between code data and character data must be stored outside the database. .

[0003]

In this conventional database system, it was necessary to select whether to have a field of a certain record as character data or as code data. When character data is selected, it is easy to display and input, but the size (required capacity) of the database becomes large, and it is wasteful especially when there is a high possibility that the same character string will be entered, such as name and affiliation. On the other hand, if the code data is selected, the size of the database becomes smaller, but there is a drawback that the input and display are difficult to understand.

An object of the present invention is to provide a database system that is easy to understand for display and input and has a small required capacity.

[0005]

A first database system of the present invention is a database system having character data as an element of a record, and a database main body for encoding the record and recording it as code data, and the code. It is provided with a correspondence means for indicating the correspondence between the data and the character data, and a conversion means for searching for the correspondence between the code data and the character data and mutually converting them. The code data is preferably an integer value. It may also be composed of an alphanumeric code, if necessary.

A second database system of the present invention is
A database system having character data as an element of a record, wherein, of the records, a record of a field of a predetermined size or less is encoded and recorded as code data, a database main body, the code data and the character data. It is provided with a correspondence means for indicating correspondence and a conversion means for searching the correspondence between the code data and the character data and mutually converting them. The code data is preferably an integer value. It may also be composed of an alphanumeric code, if necessary.

[0007]

In the database system of the present invention, the field of the record has both the character data attribute and the code data attribute. Therefore, the database is provided with a corresponding portion for storing the code data and the correspondence between the code data and the character data, and the conversion between the code data and the character data is performed by this correspondence.

[0008]

Embodiments of the present invention will now be described with reference to the drawings.

FIG. 1 is a block diagram of a database system which is an embodiment of the present invention, FIG. 2 is a flow chart showing the operation at the time of registration of this embodiment, and FIG. 3 is the display operation of this embodiment and the search operation at the time of printing. It is a flowchart showing. The database body 10 is a record 10 including a plurality of fields 1000 having character data and code data as elements.
A set of 0s, a set of code corresponding character strings 300 which is a code / character string correspondence table as a correspondence means showing correspondence between code data and character data, and a field corresponding pointer 200 for designating to the code corresponding character string 300. Consists of.
The main body of the database is the record 100 of the field 1000 of a predetermined size or smaller among the set of records 100.
Is encoded and recorded as code data. Input section 2
0 inputs character data or code data. display·
The printing unit 30 displays and prints the character string in the code corresponding character string 300 corresponding to the code of the field 1000 in the record 100 searched by the search 40 described later. The search unit 40 searches the character string of the field 1000 in the record 100 in the code-corresponding character string 300 (code → character string or character string → search for code), and also selects code → character string or character string → code. It is a conversion means for performing mutual conversion.

Here, of the set of records 100, the record 100 of the field 1000 having a predetermined size or smaller
The reason for encoding is explained. The encoding of character data is effective when a plurality of fields having the same content appear in different records. Larger fields are more likely to be memos and less likely identical fields to appear. It also takes time to find the corresponding code from the string. Therefore, in this embodiment, the record 100 of the field 1000 having a size equal to or smaller than the predetermined size is encoded.

Next, the operation of this embodiment will be described. In principle, field 1000 stores code data (integer value). Character data corresponding to the integer value is registered in the code corresponding character string 300. Ie, field 1000
The integer value of is treated as an index value to the code corresponding character string 300. Multiple records 1 with the same character data
When it appears in 00, the same index value is entered in the corresponding field 1000 of each record 100, and the same character string in the code corresponding character string 300 is designated.
Therefore, when inputting data, the code can be input as it is or a character string can be input. When inputting a character string, an arbitrary character string is input from the input unit 20, and as shown in FIG. 2, the search unit 40 has the index value of the corresponding field, that is, the character string is already registered. It is searched (step S21), and if it exists, the index value is assigned to the corresponding field 1000 (step S23). If it does not exist, the search unit 40 newly registers it in the code corresponding character string 300 (step S2).
2), new corresponding code data (code corresponding character string 30
The index value of 0) is written in the corresponding field 1000 (step S23). At the time of search, as shown in FIG. 3, the search key is searched by the code-corresponding character string 300 (step S31), and the corresponding field 1000 of each record 100 is searched by the index value (code data) (step S32). At the time of displaying and printing, a character string is searched for with the code corresponding character string 300 from the code data (index value) in the field 1000 of the corresponding record 100, and is displayed and printed. Thus, in this embodiment, easy-to-understand character data is used for display and input,
The required capacity can be reduced by using code data for the field record. Moreover, it is possible to handle this database without making the user of the database aware of the code.

[0012]

As described above, according to the present invention, the code data is stored in the record and the correspondence between the code data and the character data is stored, and the conversion between the code data and the character data is performed by this correspondence. Thus, it is possible to realize a database system that is easy to understand and easy to display and input and has a small size.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a database system that is an embodiment of the present invention.

FIG. 2 is a flowchart showing an operation at the time of registration of this embodiment.

FIG. 3 is a flowchart showing a search operation during display and printing according to the present exemplary embodiment.

[Explanation of symbols]

 10 database main body 20 input section 30 display / print section 40 search section 100 record 200 field compatible pointer 300 code compatible character string 1000 field

Claims (6)

[Claims] 1. A database system having character data as an element of a record, wherein the database main body encodes the record and records the code data as code data, and a correspondence unit indicating correspondence between the code data and the character data. A database system comprising: a conversion unit that searches for a correspondence between the code data and the character data and mutually converts the data. 2. The database system according to claim 1, wherein the code data is an integer value. 3. The database system according to claim 1, wherein the code data is an alphanumeric code. 4. A database system having character data as an element of a record, wherein a database main body which encodes a record of a field having a predetermined size or less among the records and records the code as the code data, A database system comprising: a correspondence unit that indicates a correspondence between the character data and a conversion unit that searches for a correspondence between the code data and the character data and mutually converts the correspondence. 5. The database system according to claim 4, wherein the code data is an integer value. 6. The database system according to claim 4, wherein the code data is an alphanumeric code.