| dc.contributor.author |
LORENTZOS, NA |
en |
| dc.date.accessioned |
2014-06-06T06:42:43Z |
|
| dc.date.available |
2014-06-06T06:42:43Z |
|
| dc.date.issued |
1994 |
en |
| dc.identifier.issn |
1041-4347 |
en |
| dc.identifier.uri |
http://62.217.125.90/xmlui/handle/123456789/778 |
|
| dc.subject |
COMPOSITE NUMBER |
en |
| dc.subject |
DATA MODELING |
en |
| dc.subject |
DATA TYPE |
en |
| dc.subject |
TEMPORAL DATA |
en |
| dc.subject |
TEMPORAL DATABASE |
en |
| dc.subject |
TIME DURATION |
en |
| dc.subject |
TIME POINT |
en |
| dc.subject |
TIME UNIT |
en |
| dc.subject.classification |
Computer Science, Artificial Intelligence |
en |
| dc.subject.classification |
Computer Science, Information Systems |
en |
| dc.subject.classification |
Engineering, Electrical & Electronic |
en |
| dc.subject.other |
EXTENDING RELATIONAL ALGEBRA |
en |
| dc.subject.other |
DATA MODEL |
en |
| dc.subject.other |
TIME |
en |
| dc.title |
DBMS SUPPORT FOR NONMETRIC MEASUREMENT SYSTEMS |
en |
| heal.type |
journalArticle |
en |
| heal.language |
English |
en |
| heal.publicationDate |
1994 |
en |
| heal.abstract |
In commercial DBMS's, it is possible to model only primitive numeric data types and perform arithmetic between them. In practice, however, organizations need to store and manipulate more complex numeric elements that could be interpreted as representing quantities of a non-numeric measurement system like that in which a distance is expressed in feet and inches, or like that in which a weight is expressed in quarters, stones, pounds, and ounces. This implies that users have to choose between two options, either to abandon the nonmetric system and completely adapt their applications to the limited capabilities of the DBMS or to write their own pieces of code for the management of such more-complex numeric data types. The first approach is principally unacceptable, and at the same time, there is a loss in the precision of arithmetic operations, because quantities have to be expressed as real numbers. The second one is tedious, because distinct pieces of code have to be written for handling different nonmetric units. Furthermore, integrity checking for these pieces of data has to be performed by application programs rather than by the DBMS. To overcome these problems, a new generic data type is proposed, the composite number, whose support automatically enables the use of any nonmetric measurement system. Functions and operations are defined for the management of composites. Because, in practice, time is usually expressed in many distinct nonmetric measurement units whose choice depends on the particular application, temporal databases represent one of the many application areas of the proposed formalization. |
en |
| heal.publisher |
IEEE COMPUTER SOC |
en |
| heal.journalName |
IEEE TRANSACTIONS ON KNOWLEDGE AND DATA ENGINEERING |
en |
| dc.identifier.issue |
6 |
en |
| dc.identifier.volume |
6 |
en |
| dc.identifier.isi |
ISI:A1994PT15400008 |
en |
| dc.identifier.spage |
945 |
en |
| dc.identifier.epage |
953 |
en |