Proceedings of the 48th Annual Southeast Regional Conference 2010
DOI: 10.1145/1900008.1900067
|View full text |Cite
|
Sign up to set email alerts
|

A comparison of a graph database and a relational database

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
151
0
9

Year Published

2014
2014
2023
2023

Publication Types

Select...
4
4
2

Relationship

0
10

Authors

Journals

citations
Cited by 293 publications
(161 citation statements)
references
References 3 publications
1
151
0
9
Order By: Relevance
“…marking certain classes in a UML view as being 'unsafe'. Using an SQL database to query large attributed relational data can pose efficiency problems if this requires multiple-table joins [45,46]. To alleviate this, we adopted the following schema (see Fig.…”
Section: Source Codementioning
confidence: 99%
“…marking certain classes in a UML view as being 'unsafe'. Using an SQL database to query large attributed relational data can pose efficiency problems if this requires multiple-table joins [45,46]. To alleviate this, we adopted the following schema (see Fig.…”
Section: Source Codementioning
confidence: 99%
“…Provenance can be represented as a DAG, and there is work on querying provenance graph databases [19,25]. Our study focuses on the continuous querying of massive provenance data streams.…”
Section: Related Workmentioning
confidence: 99%
“…После этапа разбора атрибуты и их значения записы-ваются в нереляционную систему управления базами данных (NoSQL), адаптированную (специально сформированную) для хранения слабоструктурированных данных. Выбор нереляционной базы данных обусловлен необходимостью быстрой обработки слабоструктурированных данных и быстрого доступа к ним [11]. Процесс проведения постинцидентного внутреннего аудита изображен на рис.…”
Section: описание методаunclassified