- What does phoenixgao/laravel-postgres-extended-schema do?
- It is a Laravel package that extends Laravel's database schema builder so migrations can define PostgreSQL-specific structures that the default builder does not expose. You keep using Laravel's familiar Schema and Blueprint API in your migration files instead of dropping into raw SQL. The package is published on Packagist as phoenixgao/laravel-postgres-extended-schema, with source on GitHub.
- How do I install phoenixgao/laravel-postgres-extended-schema with Composer?
- Run composer require phoenixgao/laravel-postgres-extended-schema from the root of your Laravel project. Laravel's package auto-discovery should register the service provider automatically, but check the README for any additional provider registration or config publishing step. Once installed, the extended schema methods are available inside your migration files as usual.
- Which Laravel and PHP versions does this package support?
- The supported Laravel and PHP ranges are declared in the package's composer.json and summarised in the README, so check those constraints before installing. Because the package hooks into the schema builder, confirm compatibility before upgrading to a new major Laravel release. Running composer why-not phoenixgao/laravel-postgres-extended-schema is a quick way to see which constraint is blocking installation.
- Do I need to replace Laravel's default schema builder to use it?
- In most setups no manual replacement is needed, because the package registers a service provider that extends or swaps the schema builder through Laravel's normal resolution. If your application or another package also overrides the schema builder, verify the registration order. The README is the authoritative source for any setup beyond a plain Composer install.
- Which PostgreSQL-specific features does it add to Laravel migrations?
- It adds PostgreSQL-oriented schema capabilities so you can declare structures in migrations that Laravel's stock builder does not support directly. The exact set of column types, indexes and constraints is documented in the README, so review it before designing your migrations. Anything not yet covered can still be handled with raw SQL statements inside the same migration.
- Will it break my existing Laravel migrations?
- Because it plugs into Laravel's schema builder, migrations that use standard Blueprint methods should continue to work unchanged. The main risk area is other packages that also customise the schema builder, since two packages can conflict over the same resolution. Running your migration suite against a test database will quickly surface any issues.
- Can I test this package with SQLite or an in-memory database?
- The package targets PostgreSQL, so tests should run against a real PostgreSQL connection rather than SQLite or an in-memory database. Postgres-specific column types and constraints generally cannot be created on other drivers. Use a containerised Postgres service in CI, or a dedicated local test database, for reliable migration tests.
- Is it safe to use in production migrations?
- As with any migration, review the generated SQL before deploying and take a backup of production data first. Postgres-specific features may require a minimum PostgreSQL server version, and some operations take table locks. Run the migrations in staging first and prefer additive, reversible changes where possible.
- How do I roll back migrations that use Postgres-specific schema features?
- Rollback depends on whether the objects you create have a down method defined in your migration. Standard Blueprint methods reverse cleanly, while raw SQL statements need a matching manual drop in down(). Always exercise the rollback path in a non-production environment before relying on it.
- What are the alternatives to this package for Postgres-specific migrations?
- The main alternative is writing DB::statement calls with raw PostgreSQL SQL inside your migrations, which works but loses the fluent feel of the schema builder. This package exists to keep advanced Postgres definitions inside Laravel's familiar API. Other community schema-extension packages exist, so compare feature coverage and recent maintenance activity before choosing.