Database management systems

A triplestore or RDF store is a purpose-built database for the storage and retrieval of triples through semantic queries. A triple is a data entity composed of subject–predicate–object, like "Bob is 35" (i.e., Bob's age measured in years is 35) or "Bob knows Fred".

theoretical realm of databases and database management systems

theory of relational databases

data persistence software system that allows data to be specified, and sometimes stored, in XML format

unique identifier for either an entity in the modeled world or an object in the database

Wikimedia list article

In the relational data model, a superkey is any set of attributes that uniquely identifies each tuple of a relation. Because superkey values are unique, tuples with the same superkey value must also have the same non-key attribute values. That is, non-key attributes are functionally dependent on the superkey.

a database system that can make deductions (conclude additional facts) based on rules and facts stored in the (deductive) database

set of axioms used to infer all the functional dependencies on a relational database

identifier for a taxpaying entity in the United States

repository for persistently storing and managing collections of data

cache of database connections maintained by the database

RavenDB is an open-source document-oriented database written in C#, developed by RavenDB Ltd. It's built on top of the custom Voron storage engine and supports ACID transactions. RavenDB uses a SQL-like query language, (RQL), and includes native features for handling time series, graph querying, and full-text search. It is cross-platform, supported on Windows, Linux, Mac OS, AWS, Azure, and GCP and can be deployed on cloud, on-prem, and the edge, including constrained environments such as Raspberry Pi Zero. RavenDB can be deployed in distributed clusters with master-master replication.

sequence of steps used to access data in a SQL relational database management system

software for collaborating on gathering, sharing and using data

A savepoint is a way of implementing subtransactions (also known as nested transactions) within a relational database management system by indicating a point within a transaction that can be "rolled back to" without affecting any work done in the transaction before the savepoint was created. Multiple savepoints can exist within a single transaction. Savepoints are useful for implementing complex error recovery in database applications. If an error occurs in the midst of a multiple-statement transaction, the application may be able to recover from the error (by rolling back to a savepoint) with

type of database

processing data tecnology

column in database table whose value is automatically computed using other columns values or another deterministic expression

relational database query language

hierarchical and recursive queries in SQL

usually in database management

formula and data query language

collection of computer resources that are kept ready to use rather than acquired on use and released afterwards

minimum number of votes that a distributed transaction has to obtain in order to be allowed to perform an operation in a distributed system

type of meta-database management system which transparently maps multiple autonomous database systems into a single federated database

function of managing and maintaining DBMS software

computer operation that makes a set of tentative changes permanent

database management system designed to support multiple data models against a single, integrated backend