If you liked what you've learned so far, dive in!
Subscribe to get access to this tutorial plus
video, code and script downloads.
The most common thing to do in a query is to add a WHERE clause. Unfortunately, Doctrine doesn't support that. I'm kidding!
I have a search box - let's search for "Lucky Number". This isn't hooked
up yet, but it adds a query parameter ?q=lucky+number
. Let's use that to
only return categories matching that.
Back in FortuneController
, add a Request $request
argument to the controller.
Below, let's look to see if there is a q
query parameter on the URL or not.
If there is, we'll search for it, otherwise, we'll keep finding all the categories.
For the search, call a new method on the repository called search()
, and
pass in the term.
... lines 1 - 7 | |
use Symfony\Component\HttpFoundation\Request; | |
... lines 9 - 14 | |
public function homepageAction(Request $request) | |
{ | |
... lines 17 - 20 | |
$search = $request->query->get('q'); | |
if ($search) { | |
$categories = $categoryRepository->search($search); | |
} else { | |
$categories = $categoryRepository->findAllOrdered(); | |
} | |
... lines 27 - 30 | |
} | |
... lines 32 - 53 |
Back in CategoryRepository
, let's make that function:
... lines 1 - 12 | |
class CategoryRepository extends EntityRepository | |
{ | |
... lines 15 - 23 | |
public function search($term) | |
{ | |
... lines 26 - 30 | |
} | |
} |
We'll make a QueryBuilder just like before, but do the entire query in just
one statement. Start by calling createQueryBuilder()
and passing it cat
:
... lines 1 - 12 | |
class CategoryRepository extends EntityRepository | |
{ | |
... lines 15 - 23 | |
public function search($term) | |
{ | |
return $this->createQueryBuilder('cat') | |
... lines 27 - 30 | |
} | |
} |
The only thing our query needs is a WHERE clause to match the term to the
name
of the Category. Let's chain!
Use a function called andWhere()
. Don't worry - Doctrine won't add an
AND
to the query, unless it's needed. Inside, write cat.name =
. But
instead of passing the variable directly into the string like this, use a
placeholder. Type colon, then make up a term. On the next line, use setParameter
to tell Doctrine what I want to fill in for that term. So type searchTerm
,
should be replaced with $term
. This avoids SQL injection attacks, so don't
muck it up! Finally, we call getQuery()
- like before - and execute()
:
... lines 1 - 23 | |
public function search($term) | |
{ | |
return $this->createQueryBuilder('cat') | |
->andWhere('cat.name = :searchTerm') | |
->setParameter('searchTerm', $term) | |
->getQuery() | |
->execute(); | |
} | |
... lines 32 - 33 |
And just like that, we should be able to go back, refresh, and there's our "Lucky Number" category match. And on the homepage, we still see everything.
But if we just search for "Lucky", we get nothing back because we're doing
an exact match. But just like with normal SQL, we know that's easy to fix.
And you already know how: just change =
to LIKE
- just like SQL!
It's just like writing SQL people! For the parameter value, surround it by percent signs to complete things. Refresh! We've got a match!
... lines 1 - 23 | |
public function search($term) | |
{ | |
return $this->createQueryBuilder('cat') | |
->andWhere('cat.name LIKE :searchTerm') | |
->setParameter('searchTerm', '%'.$term.'%') | |
->getQuery() | |
->execute(); | |
} | |
... lines 32 - 33 |
What about adding an OR WHERE to the query? The Category
entity has an
iconKey
property, which is where we get this little bug icon. For "Lucky Number",
it's set to fa-bug
from Font Awesome. Search for that. No results of course!
Let's update our query to match on the name
OR iconKey
property. If you're
guessing that there's an orWhere()
method, you're right! If you're guessing
that I'm going to use it, you're wrong!
The string inside of the andWhere
is a mini-DQL expression. So you can
add OR cat.iconKey LIKE :searchTerm
:
... lines 1 - 23 | |
public function search($term) | |
{ | |
return $this->createQueryBuilder('cat') | |
->andWhere('cat.name LIKE :searchTerm OR cat.iconKey LIKE :searchTerm') | |
->setParameter('searchTerm', '%'.$term.'%') | |
->getQuery() | |
->execute(); | |
} | |
... lines 32 - 33 |
And the searchTerm
placeholder is already being filled in:
Refresh! Another match!
So even though there is an orWhere()
function, don't use it - it can cause
WTF moments. Imagine if Category had an enabled
property, and we built
a query like this:
$this->createQueryBuilder('cat')
->andWhere('cat.name LIKE :searchTerm')
->orWhere('cat.iconKey LIKE :searchTerm')
->andWhere('cat.enabled = :enabled')
->setParameter('searchTerm', '%'.$term.'%')
->setParameter('enabled', true)
->getQuery()
->execute();
What would the SQL look like for this? Would it have the three WHERE clauses in a row, or would it correctly surround the first two with parentheses?
SELECT * FROM category WHERE
name LIKE '%lucky%' OR iconKey LIKE '%lucky%' AND enabled = 1;
SELECT * FROM category WHERE
(name LIKE '%lucky%' OR iconKey LIKE '%lucky%') AND enabled = 1;
Doctrine does the second and the query works as expected. But it's a lot
less clear to read. Instead, think of each andWhere()
as being surrounded
by its own parentheses, and put OR statements in there.
Oh, and there's also a where()
function. Don't use it either - it removes
any previous WHERE clauses on the query, which you might be doing accidentally.
In other words, always use andWhere()
, it keeps life simple.
Hey Ali
If you're not going to add any other WHERE clauses to your query, for example WHERE id = :someId
, then for this purpose would be simpler to rely on the $qb->orWhere()
method. Otherwise, you will have to write the "OR" clause manually. Something like this
$orClause = [];
foreach($colors as $key => $color) {
$orClause[] = "color LIKE :color-$key";
$qb->setParameter("color-$key", "%$color%");
}
$orClauseString = implode(' OR ', $orClause);
$qb->andWhere($orClauseString);
I used double quotes for simplicity, and didn't test the code but it should give you an idea of what to do :)
Cheers!
Hi, I followed all instructions.. also similar user case is in course Go Pro with Doctrine.. but i am on Symfony 5.2.6 and getting this error and spend all day on it with studying more videos or QueryBuilder doctrine documentation.. but i don't understand why i am getting issue it dont matter if i put string or number to search input. Do you know what exacly this part means ["%30%", "%30%"] ???
<blockquote>
An exception
occurred while executing 'SELECT t0_.id AS id0, t0.title AS title1,
t0.status AS status2, t0.description AS description3,
t0.gps_address AS gps_address4, t0.gps_lat AS gps_lat5, t0.gps_lon
AS gps_lon6, t0.gps_status AS gps_status_7 FROM tasklist t0 WHERE
t0.id LIKE ? OR t0.title LIKE ? ORDER BY t0_.id DESC' with params
["%30%", "%30%"]:
SQLSTATE[42883]: Undefined function: 7 ERROR: operator does not exist: integer ~~ unknown
LINE 1: ...s AS gps_status_7 FROM tasklist t0 WHERE t0_.id LIKE $1 OR... ^
HINT: No operator matches the given name and argument types. You might need to add explicit type casts.
</blockquote>
$qb = $this
->createQueryBuilder('c');
if ($term) {
$qb
->andWhere('c.id LIKE :term OR c.title LIKE :term')
->setParameter('term', '%' . $term . '%');
}
return $qb
->orderBy('c.id', 'DESC')
->getQuery()
->getResult();```
Hey Miky
I believe you can't use the LIKE operator on an INT field, you would need to cast it to string first but be aware it may cause performance issuesWHERE CAST(c.id as CHAR) LIKE '%15%'
Cheers!
Hi, with help of Tarmo Leppannen from Symfony on Slack, we find solution which works
$qb
->orWhere('c.id = :id')
->setParameter(':id', (int)$term)
->orWhere('LOWER(c.title) LIKE :term')
->orWhere('c.title LIKE :term')
->orWhere('LOWER(c.gps_address) LIKE :term')
->orWhere('c.gps_address LIKE :term')
->setParameter('term', '%' . (string)$term . '%');```
Hey, I heard using raw % like this could cause security issues. Is that true ? If so, how do you replace them ? Thanks :)
Hey Christophe C.!
Hmm, I don't think that's true. My guess is (but if you have some reference, please let me know) that people were warning you from making queries using % without prepared statements - like:
// DO NOT DO THIS
->andWhere('cat.name LIKE %'.$searchTerm.'%')
This would be a problem. But, we're adding the '%' around the search term inside setParameter()
, which is used in a prepared statement. We could pass ANYTHING to setParameter
and it would be safe - that's the point of "parameters" in a prepared statement: your database engine will make sure they're used in a safe/sanitized way.
Cheers!
Hello , been having a bit of an issue with grouping ? Seems doctrine is very fussy about grouping these queries. Need a way to group a bunch of orWhere ? Found this syntax on SO but guess it's not up to date anymore for doctrine 2 ? Anyone bumped into this ?
if(!empty($searchValue)) {
$qb->setParameter('searchValue2', '%' . $searchValue . '%')
->andWhere('a.customerNote LIKE ? OR a.status LIKE ? OR a.flightNum LIKE ? OR a.convocPlace LIKE ? or a.customerNote LIKE ? or a.providerNote LIKE ? or a.departDate LIKE ?',
array(':searchValue2',':searchValue2',':searchValue2',':searchValue2',':searchValue2',':searchValue2',':searchValue2'));
}
Hey Caim,
I always try to use named placeholders instead of "?". Will it work for you?
if(!empty($searchValue)) {
$qb
->andWhere('a.customerNote LIKE :searchValue2 OR a.status LIKE :searchValue2 ...')
->setParameter('searchValue2', '%' . $searchValue . '%')
}
It works for me well.
Cheers!
I think I found a solution can use the expression builder to group them like so
if(!empty($searchValue)) {
$qb->setParameter('searchValue', '%' . $searchValue . '%');
$qb->andWhere(
$qb->expr()->orX(
$qb->expr()->like('a.customerNote', ':searchValue'),
$qb->expr()->like('a.flightNum',':searchValue')
)
);
}
Hey Caim,
Agree, it should work with expressions as well, but anyway this one is easier to read but also should work well: https://knpuniversity.com/s...
Cheers!
Hey Ali,
From the docs: https://symfony.com/doc/cur... - I see:
> Entities cannot define associations across different entity managers. If you need that, there are several alternatives that require some custom setup: https://stackoverflow.com/q...
Hope this helps.
Cheers!
// composer.json
{
"require": {
"php": ">=5.3.3, <7.3.0",
"symfony/symfony": "2.6.*", // v2.6.13
"doctrine/orm": "~2.2,>=2.2.3", // v2.4.8
"doctrine/doctrine-bundle": "~1.2", // 1.6.4
"twig/extensions": "~1.0", // v1.5.4
"symfony/assetic-bundle": "~2.3", // v2.8.2
"symfony/swiftmailer-bundle": "~2.3", // v2.3.12
"symfony/monolog-bundle": "~2.4", // v2.12.1
"sensio/distribution-bundle": "~3.0.12", // v3.0.36
"sensio/framework-extra-bundle": "~3.0", // v3.0.29
"incenteev/composer-parameter-handler": "~2.0", // v2.1.3
"hautelook/alice-bundle": "0.2.*" // 0.2
},
"require-dev": {
"sensio/generator-bundle": "~2.3" // v2.5.3
}
}
Hello team! So, I am able to fetch data from the db by passing an array as the parameter to the repository function:
The entity has a property named "colors" which is an array in MySQL DB.
/**
* @param array|null $colors
* @return CardBase[] Returns an array of CardBase objects
*/
public function findCardsWithOnlyGivenColors(array $colors)
{
$qb = $this->createQueryBuilder('c');
foreach($colors as $color)
{
$qb
->andWhere('c.colors LIKE :color')
->setParameter('color', '%'.$color.'%');
}
return $qb
->orderBy('c.id', 'ASC')
->getQuery()
->getResult()
;
}
This will ensure that the fetched data have all the array elements (all the colors available in the PARAM). My problem is that I need to make another function which will fetch data having any of the elements of the searched array but not necessarily all of its elements. Given that in this tutorial, we are adviced not to use orWhere, then how to do that? findCardsWithAnyOfGivenColors{array $colors}? Thank you very much.