Nuffing.com

Laravel ClickHouse is a database driver that integrates ClickHouse with Laravel, including Eloquent, the Query Builder, Schema Builder, and more:

• Eloquent models with non-incrementing ID support
• Query Builder with ClickHouse-specific clauses (i.e.,FINAL, ARRAY JOIN, SAMPLE)
• Schema Builder with ENGINE, PARTITION BY, ORDER BY, and LowCardinality column types
• Laravel migration support via artisan migrate
• Concurrent query execution using Guzzle’s async HTTP pool
• Dual HTTP transport options: Guzzle and Curl/phpclickhouse

ClickHouse is an open-source column-oriented database built for analytical workloads. It stores data by column rather than by row, making aggregations over large datasets fast—capable of querying billions of rows in seconds. It’s a common choice for event tracking, time-series data, and analytics dashboards where read performance at scale is the priority.

Eloquent Models

You can define Eloquent models pointing at ClickHouse the same way you would for any other database connection:

class Event extends Model
{
 protected $connection = 'clickhouse';
}
 
$events = Event::where('user_id', 1)->get();

ClickHouse doesn’t use auto-incrementing primary keys, so the driver configures models with non-incrementing IDs by default. Scopes and collections work as expected.

Query Builder with ClickHouse Extensions

The Query Builder covers standard Laravel methods and adds ClickHouse-specific clauses. The final parameter applies the FINAL modifier to a query, which forces ClickHouse to merge duplicate rows at read time—useful with the ReplacingMergeTree engine:

$events = DB::connection('clickhouse')
 ->table('events', final: true)
 ->where('user_id', 1)
 ->get();

Other extensions include PREWHERE (ClickHouse’s pre-filter for primary key columns), ARRAY JOIN, SAMPLE, LIMIT BY, and SEMI/ANTI/ASOF join types.

Schema Builder and Migrations

The Schema Builder supports ClickHouse DDL via a ClickHouseBlueprint, letting you define table engines, partition keys, order keys, and column types like LowCardinality:

Schema::connection('clickhouse')->create('events', function (ClickHouseBlueprint $table) {
 $table->engine('MergeTree()');
 $table->orderBy(['id', 'created_at']);
 $table->partitionBy('toYYYYMM(created_at)');
});

Standard artisan migrate commands work with a ClickHouse-compatible migration repository, so you can manage schema changes alongside your other databases.

Concurrent Query Execution

The package includes a Parallel helper that runs multiple queries at the same time using Guzzle’s async HTTP pool:

$results = Parallel::get([
 'users' => User::where('active', 1),
 'events' => Event::where('type', 'click'),
]);

Both users and events execute concurrently, and the results are returned as a keyed array once all queries resolve.

You can find the full documentation and source on GitHub.

EAST OF EDEN — After discovering the horrific murder of their son Abel, Adam and Eve sat down to compile a comprehensive list of possible suspects.

Declaring the case to be a real "whodunit," the first man and woman puzzled long into the night as to who could be the killer.

"Think, Adam, think. Who else could it be?" said Adam, staring at his list. "Don’t get in a rush here. Leave no stone unturned. We’re going to solve this riddle and catch the killer, whoever it may be. I didn’t do it. And I asked Eve, and she said it wasn’t her. That does narrow it down somewhat."

The couple reportedly spent several hours brainstorming potential culprits, such as "rogue fig tree" and "very aggressive breeze," before coming up with their exhaustive list of people who could have perpetrated the heinous act.

"We’re following all the clues," said Eve. "I feel like we’re getting close now. We’ll start the interview process soon and begin gathering clues. It may help to draw an outline on the ground of where the body was when we found it. I think we’re finally starting to get to the bottom of this enigma."

At publishing time, the couple had begun wondering who they could select to serve on an impartial jury.

California transplants Steve and Timpani try to be the perfect Texas hosts for Brittuni’s visit, but Steve quickly realizes he needs a sensible vehicle now that he’s about to become a dad.

Click to watch the latest sketch!

Laravel Schema Sentinel by Ahtesham at Broadway Web Service detects schema drift— to help identify when your actual database no longer matches your migrations. It builds a shadow database from your migrations, diffs it against the live schema, and can generate a corrective migration when the two diverge.

• Deep drift detection — audits tables, columns, data types, nullability, defaults, indexes, and foreign keys
• Cross-environment comparison — verify local migrations match staging or production
• Auto-generated migrations — create corrective migrations with interactive review
• Visual dashboard — built-in Livewire component for database health monitoring
• Pre-migration guard — automatically block php artisan migrate if drift is detected
• And more…

Detecting Drift

The core command runs your migrations into a temporary shadow database, then compares that shadow against your live connection:

php artisan schema:drift

It checks tables, columns, data types, nullability, defaults, indexes, and foreign keys. Running with --strict also flags columns or tables present in the live database that have no corresponding migration.

Generating a Fix

When drift is found, you can have Sentinel generate a migration to close the gap:

php artisan schema:drift --fix --interactive

Interactive mode walks you through each detected difference before writing anything. A --sql flag skips file creation and prints the migration code to the terminal for review.

Cross-Environment Comparison

You can point the diff at a different environment’s database connection instead of your local one:

php artisan schema:drift --compare-env=staging

This uses the named connection from your config/database.php, so you can verify your local migrations match what’s deployed to staging or production before running them.

Programmatic API

A Sentinel facade exposes the same diff as a DTO, which you can use in controllers, Livewire components, or admin dashboards:

use Sentinel\SchemaSentinel\Facades\Sentinel;
 
$diff = Sentinel::check(strict: true);
 
return response()->json([
 'in_sync' => !$diff->hasDifferences(),
 'drift' => $diff->toArray(),
]);

The package also ships a Blade-embeddable Livewire component for a visual health dashboard, though it only renders in local environments:

<livewire:sentinel-database-health />

The package supports Laravel 11.x through 13.x. You can find Laravel Schema Sentinel on GitHub.