Utopia framework database library is simple and lite library for managing application persistency using multiple database adapters. This library is aiming to be as simple and easy to learn and use. This library is maintained by the Appwrite team.

Although this library is part of the Utopia Framework project it is dependency free, and can be used as standalone with any other PHP project or framework.

Install using composer:

composer require utopia-php/database

Initialization:

<?php

require_once __DIR__ . '/../../vendor/autoload.php';

A list of the utopia/php concepts and their relevant equivalent using the different adapters

• Database - An instance of the utopia/database library that abstracts one of the supported adapters and provides a unified API for CRUD operation and queries on a specific schema or isolated scope inside the underlining database.
• Adapter - An implementation of an underlying database engine that this library can support - below is a list of supported adapters and supported capabilities for each Adapter.
• Collection - A set of documents stored on the same adapter scope. For SQL-based adapters, this will be equivalent to a table. For a No-SQL adapter, this will equivalent to a native collection.
• Document - A simple JSON object that will be stored in one of the utopia/database collections. For SQL-based adapters, this will be equivalent to a row. For a No-SQL adapter, this will equivalent to a native document.
• Attribute - A simple document attribute. For SQL-based adapters, this will be equivalent to a column. For a No-SQL adapter, this will equivalent to a native document field.
• Index - A simple collection index used to improve the performance of your database queries.
• Permissions - Using permissions, you can decide which roles will grant read or write access for a specific document. The special attributes $read and $write are used to store permissions metadata for each document in the collection. A permission role can be any string you want. You can use Authorization::setRole() to delegate new roles to your users, once obtained a new role a user would gain read or write access to a relevant document.

• $id - the documnet unique ID, you can set your own custom ID or a random UID will be generated by the library.
• $collection - an attribute containing the name of the collection the document is stored in.
• $read - an attribute containing an array of strings. Each string represent a specific role. If your user obtains that role he will have read access for this document.
• $write - an attribute containing an array of strings. Each string represent a specific role. If your user obtains that role he will have write access for this document.

The database document interface only supports primitives types (strings, integers, floats, and booleans) translated to their native database types for each of the relevant database adapters. Complex types like arrays or objects will be encoded to JSON strings when stored and decoded back when fetched from their adapters.

Some examples to help you get started.

Creating a database:

use PDO;
use Utopia\Database\Database;
use Utopia\Database\Adapter\MariaDB;
use Utopia\Cache\Cache;
use Utopia\Cache\Adapter\None as NoCache;

$dbHost = 'mariadb';
$dbPort = '3306';
$dbUser = 'root';
$dbPass = 'password';

$pdo = new PDO("mysql:host={$dbHost};port={$dbPort};charset=utf8mb4", $dbUser, $dbPass, [
    PDO::MYSQL_ATTR_INIT_COMMAND => 'SET NAMES utf8mb4',
    PDO::ATTR_TIMEOUT => 3, // Seconds
    PDO::ATTR_PERSISTENT => true,
    PDO::ATTR_DEFAULT_FETCH_MODE => PDO::FETCH_ASSOC,
    PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION,
]);

$cache = new Cache(new NoCache()); // or use any cache adapter you wish

$database = new Database(new MariaDB($pdo), $cache);
$database->setNamespace('mydb');

$database->create(); // Creates a new schema named `mydb`

Creating a collection:

$database->createCollection('movies');

// Add attributes
$database->createAttribute('movies', 'name', Database::VAR_STRING, 128, true);
$database->createAttribute('movies', 'director', Database::VAR_STRING, 128, true);
$database->createAttribute('movies', 'year', Database::VAR_INTEGER, 0, true);
$database->createAttribute('movies', 'price', Database::VAR_FLOAT, 0, true);
$database->createAttribute('movies', 'active', Database::VAR_BOOLEAN, 0, true);
$database->createAttribute('movies', 'generes', Database::VAR_STRING, 32, true, true, true);

// Create an Index
$database->createIndex('movies', 'index1', Database::INDEX_KEY, ['year'], [128], [Database::ORDER_ASC]);

Create a document:

static::getDatabase()->createDocument('movies', new Document([
    '$read' => ['role:all', 'user1', 'user2'],
    '$write' => ['role:all', 'user1x', 'user2x'],
    'name' => 'Captain Marvel',
    'director' => 'Anna Boden & Ryan Fleck',
    'year' => 2019,
    'price' => 25.99,
    'active' => true,
    'generes' => ['science fiction', 'action', 'comics'],
]));

Find:

$documents = static::getDatabase()->find('movies', [
    new Query('year', Query::TYPE_EQUAL, [2019]),
]);

Below is a list of supported adapters, and thier compatibly tested versions alongside a list of supported features and relevant limits.

✅ - supported, 🛠 - work in progress

• CRUD: Updated databases list method
• CRUD: Validate original document before editing $id
• CRUD: Test no one can overwrite exciting documents/collections without permission
• FIND: Test for find timeout limits
• FIND: Add a query validator (Limit queries to indexed attaributes only?)
• FIND: Add support for more operators (search/match/like)
• TEST: Missing Collection, DocumentId validators tests
• TEST: Validate row size is not larger than allowed by adapter (MySQL/MariaDB ~16k)
• TEST: Add test for creation of a unique index

• In queries for arrays, should we create a dedicated index?

• ID max size can be 255 bytes
• ID can only contain [^A-Za-z0-9]
• Document max size is x bytes
• Collection can have a max of x attributes
• Collection can have a max of x indexes
• Index value max size is x bytes. Values over x bytes are truncated

Utopia Framework requires PHP 7.3 or later. We recommend using the latest PHP version whenever possible.

To run all unit tests, use the following Docker command:

docker-compose exec tests vendor/bin/phpunit --configuration phpunit.xml tests

To run static code analysis, use the following Psalm command:

docker-compose exec tests vendor/bin/psalm --show-info=true

Three commands have been added to bin/ to fill, index, and query the DB to test changes:

• bin/load invokes bin/tasks/load.php
• bin/index invokes bin/tasks/index.php
• bin/query invokes bin/tasks/query.php

To test your DB changes under load:

docker-compose exec tests bin/load --adapter=[adapter] --limit=[limit] [--name=[name]]

# [adapter]: either 'mongodb' or 'mariadb', no quotes
# [limit]: integer of total documents to generate
# [name]: (optional) name for new database

docker-compose exec tests bin/index --adapter=[adapter] --name=[name]

# [adapter]: either 'mongodb' or 'mariadb', no quotes
# [name]: name of filled database by bin/load

docker-compose exec tests bin/query --adapter=[adapter] --limit=[limit] --name=[name]

# [adapter]: either 'mongodb' or 'mariadb', no quotes
# [limit]: integer of query limit (default 25)
# [name]: name of filled database by bin/load

docker-compose exec tests bin/compare

Navigate to localhost:8708 to visualize query results.

Eldad Fux

• https://twitter.com/eldadfux
• https://github.com/eldadfux

Brandon Leckemby

• https://github.com/kodumbeats
• https://blog.kodumbeats.dev

The MIT License (MIT) http:https://www.opensource.org/licenses/mit-license.php