Download the PHP package adata-team/laravel-clickhouse-migrations without Composer
On this page you can find all versions of the php package adata-team/laravel-clickhouse-migrations. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download adata-team/laravel-clickhouse-migrations
More information about adata-team/laravel-clickhouse-migrations
Files in adata-team/laravel-clickhouse-migrations
Package laravel-clickhouse-migrations
Short Description Clickhouse migrations for Laravel
License MIT
Homepage https://github.com/adata-team/laravel-clickhouse-migrations
Informations about the package laravel-clickhouse-migrations
Laravel Clickhouse Migrations
Installation
Install this package via Composer.
Publish Clickhouse configs:
Basic Usage
Create a new migration file:
Up migrations:
Down last migration:
Advanced Usage
New Migration
To create a new migration, use this command:
For example:
The new file will be located at the path specified in the configs: clickhouse.path
Table
You can use a more prepared stub from the library that contains a template for quickly adding a new table by adding the --table option:
Dictionary
You can use a more prepared stub from the library that contains a template for quickly adding a new table by adding the --table option:
Path
You can override the path to the migrations folder by passing the --path option:
If you want to use an absolute path to the file, add one more option - --realpath to the existing option:
Stub
You can use your (override) prepared stub when creating a new file, list: clickhouse.stubs:
For example:
Also you can add Handlers, with them, you can customize over one stub every time you create a file:
The class must implement the
Adata\ClickhouseMigrations\Contracts\MigrationStubHandlerContract
interface
You can pass your $parameters
, for example:
You can also register a global handler that will apply to all generated stub files: clickhouse.handlers.global
Up Migrations
Path option with Realpath
Force
To remove the interactive question during production migrations, you can use --force option:
Output
To output migrations to be applied use --output option:
Before applying the shown migrations - will display an interactive question, to remove it, you can add another --force option to this option:
Step
You can specify how many files need to be applied:
Value
0
- all files
Down Migrations
Has the same properties as in Up Migrations.
Other
You can use a singleton object smi2/phpClickHouse to query ClickHouse (used in migrations):
License
All versions of laravel-clickhouse-migrations with dependencies
illuminate/console Version ^9.21|^10.0
illuminate/contracts Version ^6.0|^7.0|^8.0|^9.0|^10.0
illuminate/filesystem Version ^8 || ^9 || ^10
illuminate/support Version ^8.0|^9.0|^10.0
smi2/phpclickhouse Version ^1.3