DBMS > 4D vs. Apache Drill vs. dBASE vs. MySQL

System Properties Comparison 4D vs. Apache Drill vs. dBASE vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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.

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

developer.4d.com

drill.apache.org/docs

www.dbase.com/support/knowledgebase

dev.mysql.com/doc

Developer

4D, Inc

Apache Software Foundation

Asthon Tate

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1984

2012

1979

1995

Current release

v20, April 2023

1.20.3, January 2023

dBASE 2019, 2019

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Server operating systems

OS X
Windows

Linux
OS X
Windows

DOS

dBase Classic
Windows

dBase Pro

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

SQL

Support of SQL

yes

close to SQL 92

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

4D proprietary IDE
PHP

C++

dBase proprietary IDE

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

yes

user defined functions

The IDE can access stored procedures in other database systems.

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

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

ACID

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

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

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Users and groups

Depending on the underlying data source

Access rights for users and roles

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.