1992
DOI: 10.1007/978-1-4471-3546-3_9
|View full text |Cite
|
Sign up to set email alerts
|

Accessing Relational and NF2 Databases Through Database Set Predicates

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

1993
1993
2009
2009

Publication Types

Select...
7

Relationship

0
7

Authors

Journals

citations
Cited by 13 publications
(9 citation statements)
references
References 2 publications
0
9
0
Order By: Relevance
“…Draxler's work offers the most details and is most similar to ours, in describing a translation process from a subset of general-purpose Prolog syntax into SQL [10]. He also offers a survey of other earlier literature describing the translation process.…”
Section: Other Related Workmentioning
confidence: 90%
See 2 more Smart Citations
“…Draxler's work offers the most details and is most similar to ours, in describing a translation process from a subset of general-purpose Prolog syntax into SQL [10]. He also offers a survey of other earlier literature describing the translation process.…”
Section: Other Related Workmentioning
confidence: 90%
“…The relationship between the expressive powers of Datalog and relational algebra has long been recognized [1,6,18], although few systems that analyze the practical use of Datalog or Prolog together with database management systems have actually been built [7,10,11,13]. Draxler's work offers the most details and is most similar to ours, in describing a translation process from a subset of general-purpose Prolog syntax into SQL [10].…”
Section: Other Related Workmentioning
confidence: 93%
See 1 more Smart Citation
“…The SQL code in particular is generated using a Prolog to SQL translator based on the excellent work of Draxler [12]. Modifications were made to the code of [12] so that the compiler can deal with the different idioms used by different databases, the different types supported, etc.…”
Section: External Database Implementationmentioning
confidence: 99%
“…This approach does not exploit query optimization and causes many requests involving large amounts of data. Alternatively, one could either write a mixture of Prolog and SQL or automate part of this process, as covered by the Prolog to SQL converter of Draxler [3]. Our own (unpublished) experiences indicate a simple database query is at best 100 and in practice often over 1,000 times slower than using the internal Prolog database.…”
Section: Storage Optionsmentioning
confidence: 99%