References and arrow notation instead of join operation in query languages
We study properties of the join operation in query languages and describe some of its major drawbacks. We provide strong arguments against using joins as a main construct for retrieving related data elements in general purpose query languages and argue for using references instead. Since conventiona...
Main Author: | |
---|---|
Format: | Article |
Language: | English |
Published: |
Institute of Mathematics and Computer Science of the Academy of Sciences of Moldova
2012-10-01
|
Series: | Computer Science Journal of Moldova |
Subjects: | |
Online Access: | http://www.math.md/files/csjm/v20-n3/v20-n3-(pp313-333).pdf |
id |
doaj-36a4c1b3f2544010ace6c8400464836f |
---|---|
record_format |
Article |
spelling |
doaj-36a4c1b3f2544010ace6c8400464836f2020-11-24T22:44:00ZengInstitute of Mathematics and Computer Science of the Academy of Sciences of MoldovaComputer Science Journal of Moldova1561-40422012-10-01203(60)313333References and arrow notation instead of join operation in query languagesAlexandr Savinov0SAP Research Dresden, SAP AG, Chemnitzer Str. 48, 01187 Dresden, GermanyWe study properties of the join operation in query languages and describe some of its major drawbacks. We provide strong arguments against using joins as a main construct for retrieving related data elements in general purpose query languages and argue for using references instead. Since conventional references are quite restrictive when applied to data modeling and query languages, we propose to use generalized references as they are defined in the concept-oriented model (COM). These references are used by two new operations, called projection and de-projection, which are denoted by right and left arrows and therefore this access method is referred to as arrow notation. We demonstrate advantages of the arrow notation in comparison to joins and argue that it makes queries simpler, more natural, easier to understand, and the whole query writing process more productive and less error-prone.http://www.math.md/files/csjm/v20-n3/v20-n3-(pp313-333).pdfData modelingquery languagesconcept-oriented modeljoinreferencearrow notationdata semantics |
collection |
DOAJ |
language |
English |
format |
Article |
sources |
DOAJ |
author |
Alexandr Savinov |
spellingShingle |
Alexandr Savinov References and arrow notation instead of join operation in query languages Computer Science Journal of Moldova Data modeling query languages concept-oriented model join reference arrow notation data semantics |
author_facet |
Alexandr Savinov |
author_sort |
Alexandr Savinov |
title |
References and arrow notation instead of join operation in query languages |
title_short |
References and arrow notation instead of join operation in query languages |
title_full |
References and arrow notation instead of join operation in query languages |
title_fullStr |
References and arrow notation instead of join operation in query languages |
title_full_unstemmed |
References and arrow notation instead of join operation in query languages |
title_sort |
references and arrow notation instead of join operation in query languages |
publisher |
Institute of Mathematics and Computer Science of the Academy of Sciences of Moldova |
series |
Computer Science Journal of Moldova |
issn |
1561-4042 |
publishDate |
2012-10-01 |
description |
We study properties of the join operation in query languages and describe some of its major drawbacks. We provide strong arguments against using joins as a main construct for retrieving related data elements in general purpose query languages and argue for using references instead. Since conventional references are quite restrictive when applied to data modeling and query languages, we propose to use generalized references as they are defined in the concept-oriented model (COM). These references are used by two new operations, called projection and de-projection, which are denoted by right and left arrows and therefore this access method is referred to as arrow notation. We demonstrate advantages of the arrow notation in comparison to joins and argue that it makes queries simpler, more natural, easier to understand, and the whole query writing process more productive and less error-prone. |
topic |
Data modeling query languages concept-oriented model join reference arrow notation data semantics |
url |
http://www.math.md/files/csjm/v20-n3/v20-n3-(pp313-333).pdf |
work_keys_str_mv |
AT alexandrsavinov referencesandarrownotationinsteadofjoinoperationinquerylanguages |
_version_ |
1725693444607705088 |