- Does schulzefelix/laravel-bigquery support Laravel 8 or PHP 7?
- No. Release 1.7.0 drops PHP 7 and Laravel 8 and below. It targets PHP 8+ and Laravel 9+ on currently supported Laravel versions. Legacy applications should pin the last compatible package release until they upgrade their platform.
- What are the PHP and Laravel requirements for laravel-bigquery 1.7.0?
- Version 1.7.0 requires PHP 8+ and Laravel 9+, and it updates symfony/cache. Confirm the exact Composer constraints in the package's composer.json and CI matrix before adopting it. It is not fit for applications still on PHP 7 or Laravel 8 or earlier.
- How do I install and configure schulzefelix/laravel-bigquery?
- Install the package with Composer and ensure your application is on PHP 8+ and Laravel 9+. Configure Google Cloud credentials through Laravel's config and environment variables, and resolve the package through Laravel's service container. Confirm the package's configuration publishing step and grant the credentials BigQuery permissions.
- How does authentication work for Google BigQuery in this Laravel package?
- Authentication and configuration are managed through Laravel's config and service container, so you provide Google Cloud credentials in your application configuration or environment. Use a service account or application default credentials with the necessary BigQuery IAM roles. Avoid hard-coding credentials in source control.
- Can I run raw SQL queries against BigQuery using laravel-bigquery?
- Yes. The package supports running raw SQL in addition to its fluent, Eloquent-style query builder. Raw SQL is useful for complex BigQuery queries that are awkward to express through the builder. Use parameterized queries where possible to avoid unsafe string interpolation.
- How does the Eloquent-style query builder work with BigQuery?
- The package provides a fluent, Eloquent-style builder for querying BigQuery tables from a Laravel application. It lets you express simpler queries without writing raw SQL for every operation. For complex SQL, use the package's raw SQL support instead.
- Will upgrading laravel-bigquery to 1.7.0 break my cache behavior?
- Version 1.7.0 updates symfony/cache, which can change cache adapter behavior depending on your prior symfony/cache version and cache driver. Potential impact includes serialization, TTL handling, locking, and cache tag invalidation. Review the changelog and package tests, then run cache-behavior tests before upgrading.
- Which cache drivers should I test with laravel-bigquery 1.7.0?
- The package context does not list a definitive driver matrix, so verify the package's CI matrix and documentation. Test Redis, Memcached, database, file, and array drivers if your application uses them. Pay particular attention to serialization, TTLs, cache tags, locks, and atomic operations.
- Is laravel-bigquery 1.7.0 safe for production?
- Treat 1.7.0 as medium risk on PHP 8+ and Laravel 9+, and high risk for legacy estates. It is a compatibility-gated upgrade: confirm Composer constraints, symfony/cache resolution, and cache behavior first. Run unit, integration, and cache tests, then canary a low-risk application before rolling out in waves.
- What are alternatives to laravel-bigquery for querying BigQuery from Laravel?
- The main alternative is using Google Cloud's official BigQuery PHP client directly. This package adds Laravel integration such as config, service-container binding, and an Eloquent-style query builder. Choose it if those Laravel-native conveniences matter more than depending on a direct client.