Download the PHP package makinacorpus/goat-query-bundle without Composer
On this page you can find all versions of the php package makinacorpus/goat-query-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download makinacorpus/goat-query-bundle
More information about makinacorpus/goat-query-bundle
Files in makinacorpus/goat-query-bundle
Package goat-query-bundle
Short Description Symfony bundle for makinacorpus/goat-query
License GPL-2.0-or-later
Homepage http://github.com/pounard/goat-query-bundle
Informations about the package goat-query-bundle
Goat Query Symfony bundle
This packages provides autoconfiguration and integration of makinacorpus/goat-query for the Symfony framework.
Installation
Then add the following bundles into your Symfony config/bundles.php
file:
Usage
If everything was successfuly configured, you may use one of the following classes in dependency injection context (ie. services constructor arguments or controllers action methods parameters):
-
Goat\Runner\Runner
gives you a runner instance plugged onto the default Doctrine DBAL connection, Goat\Query\QueryBuilder
gives you a query factory instance.
Configuration
Manual configuration (standalone)
Manually configuring your connections is as simple as:
Automatic configuration (side by side with Doctrine)
Per default, if you installed and configured Doctrine in Symfony, this bundle will create one runner per Doctrine connexion, re-using Doctrine DBAL PDO connexion for each one, sharing its sessions.
Considering the following Doctrine configuration:
You will obtain a single Goat\Runner\Runner
instance in the container,
named goat.runner.default
.
Using a more advanced configuration, such as:
You will obtain 2 different runners:
goat.runner.default
goat.runner.logging
No further configuration is required.
Advanced configuration
Runners
A runner is a connection, you may have one or more. Per default, you should
always configure the default
connection.
Re-using a Doctrine connection
Using the ext-pgsql driver
You will notice that for ext-pgsl
we do not configure a metadata cache,
because ext-pgsql
is very fast and using APCu to store metadata doesn't
bring any performance boost (it would slower the runner actually).
Using <any> driver
The previous section works for any driver, just replace all ext-pgsql
section
by any of:
ext-pgsql
: for PostgreSQL via PHPext-pgsql
,pdo-pgsql
: for PostgreSQL viaPDO
,pgsql
: for PostgreSQL via driver autoselection (ext-pgsql
is prefered),pdo-mysql
: for MySQL viaPDO
,mysql
: for MySQL via driver autoselection (onlyPDO
is supported right now).
More than one database connexion
The default
runner is the one that per default will be injected into services
using the \Goat\Runner\Runner
interface as type-hint when using autowiring.
In order to inject a specific runner, you may use the goat.runner.NAME
service
identifier, in the above example, you would have the following two services
available:
goat.runner.default
, the default one,goat.runner.logging
, the other one.
Driver configuration
Read the `` file in this package for more information.
@todo
All versions of goat-query-bundle with dependencies
makinacorpus/profiling Version ^1.1.1 || ^2.0.1
php Version >=7.4
psr/log Version ^1.0 || ^2 || ^3