Abstract

We aspire to make one query reasonably sufficient to extract data regardless of the data model used in our research. In such a way, users can freely use any query language they master to interrogate the heterogeneous database, not necessarily the query language associated with the model. Thus, overcoming the needing to deal with multiple query languages, which is, usually, an unwelcome matter for non-expert users and even for the expert ones. To do so, we proposed a new translation approach, relying on an intermediate query language to convert the user query into a suitable query language, according to the nature of data interrogated. Which is more beneficial rather than repeat the whole process for each new query submission. On the other hand, this empowers the system to be modular and divided into multiple, more flexible, and less complicated components. Therefore, it increases possibilities to make independent transformations and to switch between several query languages efficiently. By using our system, querying each data model with the corresponding query language is no longer bothersome. As a start, we are covering the eXtensible Markup Language (XML) and relational data models, whether native or hybrid. Users can retrieve data sources over these models using just one query, expressed with either the XML Path Language (XPath) or the Structured Query Language (SQL).

Highlights

  • The relational database has been the most data model used in most organizations to store and manage data

  • We generate an intermediate query language that reflects the logical interpretation of the query. We called it the universal query language (UQL); a transitional phase that provides an intermediate representation to switch between steps accurately, instead of converting the source query language directly to the target query language

  • Because we are covering XML and relational database models, we need to define the grammar of their query languages, namely XML Path Language (XPath) and Structured Query Language (SQL)

Read more

Summary

INTRODUCTION

The relational database has been the most data model used in most organizations to store and manage data. Some researchers focused on storing and querying XML data using a relational database system [1] [2]. We generate an intermediate query language that reflects the logical interpretation of the query. We called it the universal query language (UQL); a transitional phase that provides an intermediate representation to switch between steps accurately, instead of converting the source query language directly to the target query language. The system is capable of performing queries against XML and relational databases and against hybrid ones too.

Describing a Language using a Grammar
Grammar Notation
AIMS AND MECHANISMS
Diagrammatic Form
Parsing Queries
LANGUAGE RECOGNITION AND PROCESSING
Query Language Specifications
INTERMEDIATE REPRESENTATION
11. Abstract
DATA EXTRACTION
CONCLUSION AND OUTLOOK

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.