SingleStore Driver for Laravel
This repository contains a SingleStore Driver for Laravel.
Install
You can install the package via composer:
composer require singlestoredb/singlestoredb-laravel
Usage
To enable the driver, head to your config/database.php
file and create a new entry for SingleStore in your connections
, and update your default
to point to that new connection:
[
'default' => env('DB_CONNECTION', 'singlestore'),
'connections' => [
'singlestore' => [
'driver' => 'singlestore',
'url' => env('DATABASE_URL'),
'host' => env('DB_HOST'),
'port' => env('DB_PORT'),
'database' => env('DB_DATABASE'),
'username' => env('DB_USERNAME'),
'password' => env('DB_PASSWORD'),
'unix_socket' => env('DB_SOCKET'),
'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
'prefix' => '',
'prefix_indexes' => true,
'strict' => true,
'engine' => null,
'options' => extension_loaded('pdo_mysql') ? array_filter([
PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
PDO::ATTR_EMULATE_PREPARES => true,
]) : [],
],
]
]
The SingleStore driver is an extension of the MySQL driver, so you could also just change your
driver
frommysql
tosinglestore
.
In case you want to store failed jobs in SingleStore, then make sure you also set it as the database
in your config/queue.php
file. At which point, you may actually prefer to set DB_CONNECTION='singlestore'
in your environment variables.
'failed' => [
'driver' => env('QUEUE_FAILED_DRIVER', 'database-uuids'),
'database' => env('DB_CONNECTION', 'singlestore'),
'table' => 'failed_jobs',
],
PHP Versions before 8.1
In PHP versions before 8.1, the flag PDO::ATTR_EMULATE_PREPARES
results in a bug by which all attributes returned by MySQL (and SingleStoreDB) are returned as strings.
For example, a table with a column named user_id
and a type of int(10)
, if the row value is 5423
we would get a string like "5423"
in PHP.
This is a historic and known bug:
- https://stackoverflow.com/a/58830039/3275796
- https://github.com/php/php-src/blob/7b34db0659dda933b1146a0ff249f25acca1d669/UPGRADING#L130-L134
The best method to solve this is to upgrade to PHP 8.1 or higher. If that's not possible, Eloquent's attribute casting is the next best solution.
Migrations
This driver provides many SingleStore specific methods for creating or modifying tables. They are listed below. For more information see the Create Table docs on SingleStore.
Rowstore Tables
To create a rowstore table, use the rowstore
method.
Schema::create('table', function (Blueprint $table) {
$table->rowstore();
// ...
});
Reference Tables
To create a reference table, you may use the reference
method.
Schema::create('table', function (Blueprint $table) {
$table->reference();
// ...
});
Global Temporary Tables
To create a global temporary table, you may use the global
method on the table.
Schema::create('table', function (Blueprint $table) {
$table->rowstore();
$table->temporary();
$table->global();
// ...
});
You may also use either of the following two methods:
// Fluent
$table->rowstore()->temporary()->global();
// As an argument to `temporary`.
$table->temporary($global = true);
Sparse Columns
You can mark particular columns as sparse fluently by appending sparse
to the column's definition.
Schema::create('table', function (Blueprint $table) {
$table->rowstore();
$table->string('name')->nullable()->sparse();
});
Sparse Tables
You can mark particular entire tables as sparse fluently by appending sparse
to the column's definition.
Schema::create('table', function (Blueprint $table) {
$table->rowstore();
$table->string('name');
$table->sparse();
});
Shard Keys
You can add a shard key to your tables using the standalone shardKey
method, or fluently by appending shardKey
to the column definition.
Schema::create('table', function (Blueprint $table) {
$table->string('name');
$table->shardKey('name');
});
Schema::create('table', function (Blueprint $table) {
$table->string('name')->shardKey();
});
Schema::create('table', function (Blueprint $table) {
$table->string('f_name');
$table->string('l_name');
$table->shardKey(['f_name', 'l_name']);
});
Sort Keys
You can add a sort key to your tables using the standalone sortKey
method, or fluently by appending sortKey
to the column definition.
Schema::create('table', function (Blueprint $table) {
$table->string('name');
$table->sortKey('name');
});
Schema::create('table', function (Blueprint $table) {
$table->string('name')->sortKey();
});
Schema::create('table', function (Blueprint $table) {
$table->string('f_name');
$table->string('l_name');
$table->sortKey(['f_name', 'l_name']);
});
Series Timestamps
To denote a column as a series timestamp, use the seriesTimestamp
column modifier.
Schema::create('table', function (Blueprint $table) {
$table->datetime('created_at')->seriesTimestamp();
// Or make it sparse
$table->datetime('deleted_at')->nullable()->seriesTimestamp()->sparse();
});
Computed Columns
SingleStore does not support virtual computed columns. You must use Laravel's storedAs
method to create a persisted computed column.
Schema::create('test', function (Blueprint $table) {
$table->integer('a');
$table->integer('b');
$table->integer('c')->storedAs('a + b');
});
Testing
Execute the tests using PHPUnit
./vendor/bin/phpunit
To test against an active SingleStore database, create a .env
file and populate the following variables:
DB_DATABASE=
DB_USERNAME=
DB_PASSWORD=
DB_HOST=
Now when executing your tests, enable the integration tests by running
HYBRID_INTEGRATION=1 ./vendor/bin/phpunit
License
This library is licensed under the Apache 2.0 License.
Resources
User agreement
SINGLESTORE, INC. ("SINGLESTORE") AGREES TO GRANT YOU AND YOUR COMPANY ACCESS TO THIS OPEN SOURCE SOFTWARE CONNECTOR ONLY IF (A) YOU AND YOUR COMPANY REPRESENT AND WARRANT THAT YOU, ON BEHALF OF YOUR COMPANY, HAVE THE AUTHORITY TO LEGALLY BIND YOUR COMPANY AND (B) YOU, ON BEHALF OF YOUR COMPANY ACCEPT AND AGREE TO BE BOUND BY ALL OF THE OPEN SOURCE TERMS AND CONDITIONS APPLICABLE TO THIS OPEN SOURCE CONNECTOR AS SET FORTH BELOW (THIS “AGREEMENT”), WHICH SHALL BE DEFINITIVELY EVIDENCED BY ANY ONE OF THE FOLLOWING MEANS: YOU, ON BEHALF OF YOUR COMPANY, CLICKING THE “DOWNLOAD, “ACCEPTANCE” OR “CONTINUE” BUTTON, AS APPLICABLE OR COMPANY’S INSTALLATION, ACCESS OR USE OF THE OPEN SOURCE CONNECTOR AND SHALL BE EFFECTIVE ON THE EARLIER OF THE DATE ON WHICH THE DOWNLOAD, ACCESS, COPY OR INSTALL OF THE CONNECTOR OR USE ANY SERVICES (INCLUDING ANY UPDATES OR UPGRADES) PROVIDED BY SINGLESTORE. BETA SOFTWARE CONNECTOR
Customer Understands and agrees that it is being granted access to pre-release or “beta” versions of SingleStore’s open source software connector (“Beta Software Connector”) for the limited purposes of non-production testing and evaluation of such Beta Software Connector. Customer acknowledges that SingleStore shall have no obligation to release a generally available version of such Beta Software Connector or to provide support or warranty for such versions of the Beta Software Connector for any production or non-evaluation use.
NOTWITHSTANDING ANYTHING TO THE CONTRARY IN ANY DOCUMENTATION, AGREEMENT OR IN ANY ORDER DOCUMENT, SINGLESTORE WILL HAVE NO WARRANTY, INDEMNITY, SUPPORT, OR SERVICE LEVEL, OBLIGATIONS WITH RESPECT TO THIS BETA SOFTWARE CONNECTOR (INCLUDING TOOLS AND UTILITIES).
APPLICABLE OPEN SOURCE LICENSE: Apache 2.0
IF YOU OR YOUR COMPANY DO NOT AGREE TO THESE TERMS AND CONDITIONS, DO NOT CHECK THE ACCEPTANCE BOX, AND DO NOT DOWNLOAD, ACCESS, COPY, INSTALL OR USE THE SOFTWARE OR THE SERVICES.