Readyset is a MySQL and Postgres wire-compatible caching layer that sits in front of existing databases to speed up queries and horizontally scale read throughput. Under the hood, ReadySet caches the results of cached select statements and incrementally updates these results over time as the underlying data changes.
The Laravel framework test fails for Postgres. We should figure out why and fix any applicable bugs.
For context, the test seems to work fine until the point that migrations start being run, but then fails on the first migration:
2014_10_12_000000_create_users_table .............................. 9ms FAIL
Illuminate\Database\QueryException
SQLSTATE[25P02]: In failed sql transaction: 7 ERROR: current transaction is aborted, commands ignored until end of transaction block (SQL: alter table "users" add constraint "users_email_unique" unique ("email"))
at vendor/laravel/framework/src/Illuminate/Database/Connection.php:760
756▕ // If an exception occurs when attempting to run a query, we'll format the error
757▕ // message to include the bindings with SQL, which will make this exception a
758▕ // lot more helpful to the developer instead of just the database's errors.
759▕ catch (Exception $e) {
➜ 760▕ throw new QueryException(
761▕ $query, $this->prepareBindings($bindings), $e
762▕ );
763▕ }
764▕ }
+9 vendor frames
10 database/migrations/2014_10_12_000000_create_users_table.php:24
Illuminate\Support\Facades\Facade::__callStatic("create")
+37 vendor frames
48 artisan:37
Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
ERROR: 1
The Laravel framework test fails for Postgres. We should figure out why and fix any applicable bugs.
For context, the test seems to work fine until the point that migrations start being run, but then fails on the first migration: