DBMS > Lovefield vs. SpatiaLite vs. SQLite vs. Valentina Server

System Properties Comparison Lovefield vs. SpatiaLite vs. SQLite vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

Spatial extension of SQLite

Widely used embeddable, in-process RDBMS

Object-relational database and reports server

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

google.github.io/lovefield

www.gaia-gis.it/fossil/libspatialite/index

www.sqlite.org

www.valentina-db.net

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

www.gaia-gis.it/gaia-sins/spatialite_topics.html

www.sqlite.org/docs.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Google

Alessandro Furieri

Dwayne Richard Hipp

Paradigma Software

Initial release

2014

2008

2000

1999

Current release

2.1.12, February 2017

5.0.0, August 2020

3.45.3 (15 April 2024), April 2024

5.7.5

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

Public Domain

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

server-less

Linux
OS X
Windows

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

yes

APIs and other access methods

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC

Supported programming languages

JavaScript

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

fine grained access rights according to SQL-standard

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.