DBMS > dBASE vs. GeoSpock vs. LokiJS vs. MySQL

System Properties Comparison dBASE vs. GeoSpock vs. LokiJS vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

Spatial and temporal data processing engine for extreme data scale

In-memory JavaScript DBMS

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	9.16
Rank	#43	Overall
	#27	Relational DBMS

Score	0.44
Rank	#256	Overall
	#40	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

www.dbase.com

geospock.com

github.com/techfort/LokiJS

www.mysql.com

Technical documentation

www.dbase.com/support/knowledgebase

techfort.github.io/LokiJS

dev.mysql.com/doc

Developer

Asthon Tate

GeoSpock

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1979

2014

1995

Current release

dBASE 2019, 2019

2.0, September 2019

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java, Javascript

JavaScript

C and C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

hosted

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

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

temporal, categorical

yes

via views

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

JDBC

JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

dBase proprietary IDE

JavaScript

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

View functions in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

not for dBase internal data, but IDE does support transactions when accessing external DBMS

atomic operations within a single collection possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users and roles

Access rights for users can be defined per table

Users with fine-grained authorization concept

no user groups or roles

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.