Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/andanteproject/shared-query-builder
A Doctrine 2 Query Builder decorator that makes easier to build your query in shared contexts
https://github.com/andanteproject/shared-query-builder
doctrine doctrine-orm php php-74 php7 query-builder
Last synced: about 1 month ago
JSON representation
A Doctrine 2 Query Builder decorator that makes easier to build your query in shared contexts
- Host: GitHub
- URL: https://github.com/andanteproject/shared-query-builder
- Owner: andanteproject
- License: mit
- Created: 2021-03-08T22:45:18.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-07-25T21:02:54.000Z (4 months ago)
- Last Synced: 2024-09-29T20:01:30.470Z (about 2 months ago)
- Topics: doctrine, doctrine-orm, php, php-74, php7, query-builder
- Language: PHP
- Homepage:
- Size: 60.5 KB
- Stars: 4
- Watchers: 2
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Shared Query Builder
#### Doctrine 2 [Query Builder](https://www.doctrine-project.org/projects/doctrine-orm/en/2.8/reference/query-builder.html) decorator - [AndanteProject](https://github.com/andanteproject)
[](https://github.com/andanteproject/shared-query-builder/releases)
A Doctrine 2 [Query Builder](https://www.doctrine-project.org/projects/doctrine-orm/en/2.8/reference/query-builder.html)
decorator that makes easier to build your query in shared contexts.
## Why do I need this?
When your query business logic is big and complex you are probably going to split its building process to different
places/classes.
Without `SharedQueryBuilder` there is no way to do that unless *guessing Entity aliases* and messing up with *join
statements*.
This [query builder](https://www.doctrine-project.org/projects/doctrine-orm/en/2.8/reference/query-builder.html)
decorator addresses some problems you can find in a real world situation you usually solve with workarounds and business
conventions.
## Features
- Ask [query builder](https://www.doctrine-project.org/projects/doctrine-orm/en/2.8/reference/query-builder.html)
which alias is used for an entity when you are outside its creation context;
- **Lazy joins** to declare join statements to be performed only if related criteria are defined;
- **Immutable** and **unique** query **parameters**;
- Works like magic ✨.
## Requirements
Doctrine 2 and PHP 7.4.
## Install
Via [Composer](https://getcomposer.org/):
```bash
$ composer require andanteproject/shared-query-builder
```
## Set up
After creating
your [query builder](https://www.doctrine-project.org/projects/doctrine-orm/en/2.8/reference/query-builder.html), wrap
it inside our `SharedQueryBuilder`.
```php
use Andante\Doctrine\ORM\SharedQueryBuilder;
// $qb instanceof Doctrine\ORM\QueryBuilder
// $userRepository instanceof Doctrine\ORM\EntityRepository
$qb = $userRepository->createQueryBuilder('u');
// Let's wrap query builder inside our decorator.
// We use $sqb as acronym of "Shared Query Builder"
$sqb = SharedQueryBuilder::wrap($qb);
```
From now on, you can use `$sqb` exactly as you usually do
with [query builder](https://www.doctrine-project.org/projects/doctrine-orm/en/2.8/reference/query-builder.html) (every
single method of `QueryBuilder` is available on `SharedQueryBuilder`), **but with some useful extra methods** 🤫.
When you're done building your query, just **unwrap** your `SharedQueryBuilder`.
```php
// $sqb instanceof Andante\Doctrine\ORM\SharedQueryBuilder
// $qb instanceof Doctrine\ORM\QueryBuilder
$qb = $sqb->unwrap();
```
#### Please note:
- The only condition applied to build a `SharedQueryBuilder` is that no join statement has to be declared yet.
- `SharedQueryBuilder` is *a decorator* of `QueryBuilder`, which means it is not an `instance of QueryBuilder` even if
it has all its methods (sadly, Doctrine has no QueryBuilder Interface 🥺).
- `SharedQueryBuilder` do not allow you to join an Entity multiple times with different aliases.
## Which additional methods do I have?
### Entity methods
You can ask the `SharedQueryBuilder` if it has and entity in the `from` statement or some `join` statements.
```php
if($sqb->hasEntity(User::class)) // bool returned
{
// Apply some query criteria only if this query builder is handling the User entity
}
```
You can ask which is the alias of an Entity inside the query you're building (no matter if it is used in a `from`
statement or a `join` statement).
```php
$userAlias = $sqb->getAliasForEntity(User::class); // string 'u' returned
```
You can use `withAlias` method to smoothly add a condition for that entity property:
```php
if($sqb->hasEntity(User::class)) // bool returned
{
$sqb
->andWhere(
$sqb->expr()->eq(
$sqb->withAlias(User::class, 'email'), // string 'u.email'
':email_value'
)
)
->setParameter('email_value', '[email protected]')
;
}
```
Given an alias, you can retrieve its entity class:
```php
$entityClass = $sqb->getEntityForAlias('u'); // string 'App\Entity\User' returned
```
`QueryBuilder::getAllAliases` is extended to have an optional `bool` argument `$includeLazy` (default:`false`) to
include [lazy joins](#lazy-join) aliases.
```php
$allAliases = $sqb->getAllAliases(true);
```
### Lazy Join
All query builder `join` methods can be used as usually, but you can also use them with "`lazy`" prefix.
```php
// Common join methods
$sqb->join(/* args */);
$sqb->innerJoin(/* args */);
$sqb->leftJoin(/* args */);
// Lazy join methods
$sqb->lazyJoin(/* args */);
$sqb->lazyInnerJoin(/* args */);
$sqb->lazyLeftJoin(/* args */);
// They works with all the ways you know you can perform joins in Doctrine
// A: $sqb->lazyJoin('u.address', 'a')
// or B: $sqb->lazyJoin('Address::class', 'a', Expr\Join::WITH, $sqb->expr()->eq('u.address','a'))
```
By doing this, you are defining a `join` statement **without actually adding it** to your DQL query. It is going to be
added to your DQL query only when you add **another condition/dql part** which refers to it. Automagically ✨.
Based on how much confused you are right now, you can check for [why you should need this](#why-do-i-need-this)
or [some examples](#examples) to achieve your "OMG" revelation moment.
## Examples
Let's suppose we need to list `User` entities but we also have an **optional filter** to search an user by it's
address `Building` name.
There is no need to perform any join until we decide to use that filter. We can use **Laxy Join** to achieve this.
```php
$sqb = SharedQueryBuilder::wrap($userRepository->createQueryBuilder('u'));
$sqb
->lazyJoin('u.address', 'a')
->lazyJoin('a.building', 'b')
//Let's add a WHERE condition that do not need our lazy joins
->andWhere(
$sqb->expr()->eq('u.verifiedEmail', ':verified_email')
)
->setParameter('verified_email', true)
;
$users = $sqb->getQuery()->getResults();
// DQL executed:
// SELECT u
// FROM App\entity\User
// WHERE u.verifiedEmail = true
// BUT if we use the same Query Builder to filter by building.name:
$buildingNameFilter = 'Building A';
$sqb
->andWhere(
$sqb->expr()->eq('b.name', ':name_value')
)
->setParameter('name_value', $buildingNameFilter)
;
$users = $sqb->getQuery()->getResults();
// DQL executed:
// SELECT u
// FROM App\entity\User
// JOIN u.address a
// JOIN a.building b
// WHERE u.verifiedEmail = true
// AND b.name = 'Building A'
```
You are probably thinking: **why don't we achieve the same result with the following, more common, way**? (keep in mind
that avoid to perform unecessary joins is still a requirement)
```php
// How you could achieve this without SharedQueryBuilder
$buildingNameFilter = 'Building A';
$qb = $userRepository->createQueryBuilder('u');
$qb
->andWhere(
$qb->expr()->eq('u.verifiedEmail', ':verified_email')
)
->setParameter('verified_email', true);
if(!empty($buildingNameFilter)){
$qb
->lazyJoin('u.address', 'a')
->lazyJoin('a.building', 'b')
->andWhere(
$qb->expr()->eq('b.name', ':building_name_value')
)
->setParameter('building_name_value', $buildingNameFilter)
;
}
$users = $qb->getQuery()->getResults(); // Same result as example shown before
// But this has some down sides further explained
```
The code above is perfectly fine if you build this whole query in the **same context**:
- 👍 You are *aware* of the whole query building process;
- 👍 You are *aware* of which entities are involved;
- 👍 You are *aware* of which alias are defined for each entity.
- 👍 You are *aware* of which query parameters are defined and their purpose.
But you have problems:
- 👎 You are mixing query structure definition with optional filtering criteria.
- 👎 Code is is quickly going to be an unreadable mess.
### A real world case
If your query structure grows with lots of joins and filtering criteria, you are probably going to split all that
business logic in different classes.
For instance, in a backoffice Users list, you are probably going to define your *main query* to list entities in your
controller and handle **optional filters** in some **other classes**.
```php
// UserController.php
class UserController extends Controller
{
public function index(Request $request, UserRepository $userRepository) : Response
{
$qb = $userRepository->createQueryBuilder('u');
$qb
->andWhere(
$qb->expr()->eq('u.verifiedEmail', ':verified_email')
)
->setParameter('verified_email', true);
// Now Apply some optional filters from Request
// Let's suppose we have an "applyFilters" method which is giving QueryBuilder and Request
// to and array of classes responsable to take care of filtering query results.
$this->applyFilters($qb, $request);
// Maybe have some pagination logic here too. Check KnpLabs/knp-components which is perfect for this.
$users = $qb->getQuery()->getResults();
// Build our response with User entities list.
}
}
```
Filter classes may look like this:
```php
// BuildingNameFilter.php
class BuildingNameFilter implements FilterInterface
{
public function filter(QueryBuilder $qb, Request $request): void
{
$buildingNameFilter = $request->query->get('building-name');
if(!empty($buildingNameFilter)){
$qb
->join('u.address', 'a')
->join('a.building', 'b')
->andWhere(
$qb->expr()->eq('b.name', ':building_name_value')
)
->setParameter('building_name_value', $buildingNameFilter)
;
}
}
}
```
**We are committing some multiple sins here! 💀 The context is changed.**
- 👎 You are *not aware* of the whole query building process. Is the given QueryBuilder even a query on User entity?;
- 👎 You are *not aware* of which entities are involved. Which entities are already been joined?;
- 👎 You are *not aware* of which aliases are defined for each entity. No way we are calling `u.address` by convention
🤨;
- 👎 You are *aware* of what parameters have been defined (`$qb->getParameters()`), but you are *not aware* why they
have been defined, for which purpose and you can also *override* them changing elsewhere behavior;
- 👎 Our job in this context is just to apply some filter. We *can* change the query by adding some join statements but
we *should avoid* that. What if another filter also need to perform those joins? Devastating. 😵
#### This's why SharedQueryBuilder is going to save your ass in these situations
Let's see how we can solve all these problems with `SharedQueryBuilder` (you can now guess why it is named like this).
Using `SharedQueryBuilder` you can:
- 👍 Define **lazy join** to allow them to be performed only if they are needed;
- 👍 Define some parameters **immutable** to be sure value is not going to be changed elsewhere;
- 👍 You can **check if an entity is involved in a query** and then apply some business logic;
- 👍 You can **ask the query builder** which *alias* is used for a specific entity so you are not going to guess aliases
or sharing them between classes using constants (I know you thought of that 🧐).
```php
// UserController.php
use Andante\Doctrine\ORM\SharedQueryBuilder;
class UserController extends Controller
{
public function index(Request $request, UserRepository $userRepository) : Response
{
$sqb = SharedQueryBuilder::wrap($userRepository->createQueryBuilder('u'));
$sqb
// Please note: Sure, you can mix "normal" join methods and "lazy" join methods
->lazyJoin('u.address', 'a')
->lazyJoin('a.building', 'b')
->andWhere($sqb->expr()->eq('u.verifiedEmail', ':verified_email'))
->setImmutableParameter('verified_email', true);
// Now Apply some optional filters from Request
// Let's suppose we have an "applyFilters" method which is giving QueryBuilder and Request
// to and array of classes responsable to take care of filtering query results.
$this->applyFilters($sqb, $request);
// Maybe have some pagination logic here too.
// You probably need to unwrap the Query Builder now for this
$qb = $sqb->unwrap();
$users = $qb->getQuery()->getResults();
// Build our response with User entities list.
}
}
```
Filter classes will look like this:
```php
// BuildingNameFilter.php
use Andante\Doctrine\ORM\SharedQueryBuilder;
class BuildingNameFilter implements FilterInterface
{
public function filter(SharedQueryBuilder $sqb, Request $request): void
{
$buildingNameFilter = $request->query->get('building-name');
// Let's check if Query has a Building entity in from or join DQL parts 🙌
if($sqb->hasEntity(Building::class) && !empty($buildingNameFilter)){
$sqb
->andWhere(
// We can ask Query builder for the "Building" alias instead of guessing it/retrieve somewhere else 💋
$sqb->expr()->eq($sqb->withAlias(Building::class, 'name'), ':building_name_value')
// You can also use $sqb->getAliasForEntity(Building::class) to discover alias is 'b';
)
->setImmutableParameter('building_name_value', $buildingNameFilter)
;
}
}
}
```
- 👍 No extra join statements executed when there is no need for them;
- 👍 No way to change/override parameters value once defined;
- 👍 We can discover if the Query Builder is handling an Entity and then apply our business logic;
- 👍 We are not guessing entity aliases;
- 👍 Our filter class is only responsible for filtering;
- 👍 There can be multiple filter class handling different criteria on the same entity without having duplicated join
statements;
#### Immutable Parameters
Shared query builder has **Immutable Parameters**. Once defined, they cannot be changed otherwise and *Exception* will
be raised.
```php
// $sqb instanceof Andante\Doctrine\ORM\SharedQueryBuilder
// set a common Query Builder parameter, as you are used to
$sqb->setParameter('parameter_name', 'parameterValue');
// set an immutable common Query Builder parameter. It cannot be changed otherwise an exception will be raised.
$sqb->setImmutableParameter('immutable_parameter_name', 'parameterValue');
// get a collection of all query parameters (commons + immutables!)
$sqb->getParameters();
// get a collection of all immutable query parameters (exclude commons)
$sqb->getImmutableParameters();
// Sets a parameter and return parameter name as string instead of $sqb.
$sqb->withParameter(':parameter_name', 'parameterValue');
$sqb->withImmutableParameter(':immutable_parameter_name', 'parameterValue');
// This allows you to write something like this:
$sqb->expr()->eq('building.name', $sqb->withParameter(':building_name_value', $buildingNameFilter));
// The two following methods sets "unique" parameters. See "Unique parameters" doc section for more...
$sqb->withUniqueParameter(':parameter_name', 'parameterValue');
$sqb->withUniqueImmutableParameter(':parameter_name', 'parameterValue');
```
#### Set parameter and use it in expression at the same moment
If you are sure you are not going to use a parameter in multiple places inside your query, you can write the following
code 🙌
```php
$sqb
->andWhere(
$sqb->expr()->eq(
$sqb->withAlias(Building::class, 'name'),
':building_name_value'
)
)
->setImmutableParameter('building_name_value', $buildingNameFilter)
;
```
this way 👇👇👇
```php
$sqb
->andWhere(
$sqb->expr()->eq(
$sqb->withAlias(Building::class, 'name'),
$sqb->withImmutableParameter(':building_name_value', $buildingNameFilter) // return ":building_name_value" but also sets immutable parameter
)
)
;
```
#### Unique parameters
Beside [immutable parameters](#immutable-parameters), you can also demand query builder the generation of a parameter
name. Using the following methods, query builder will decorate names to avoid conflicts with already declared ones (
which cannot even happen with immutable parameters).
```php
$sqb
->andWhere(
$sqb->expr()->eq(
'building.name',
$sqb->withUniqueParameter(':name', $buildingNameFilter) // return ":param_name_4b3403665fea6" making sure parameter name is not already in use and sets parameter value.
)
)
->andWhere(
$sqb->expr()->gte(
'building.createdAt',
$sqb->withUniqueImmutableParameter(':created_at', new \DateTime('-5 days ago')) // return ":param_created_at_5819f3ad1c0ce" making sure parameter name is not already in use and sets immutable parameter value.
)
)
->andWhere(
$sqb->expr()->lte(
'building.createdAt',
$sqb->withUniqueImmutableParameter(':created_at', new \DateTime('today midnight')) // return ":param_created_at_604a8362bf00c" making sure parameter name is not already in use and sets immutable parameter value.
)
)
;
/*
* Query Builder has now 3 parameters:
* - param_name_4b3403665fea6 (common)
* - param_created_at_5819f3ad1c0ce (immutable)
* - param_created_at_604a8362bf00c (immutable)
*/
```
### Conclusion
The world is a happier place 💁.
Give us a ⭐️ if your world is now a happier place too! 💃🏻
Built with love ❤️ by [AndanteProject](https://github.com/andanteproject) team.