通过中间表进行SQL查询
给出下表:
Recipes
| id | name
| 1 | 'chocolate cream pie'
| 2 | 'banana cream pie'
| 3 | 'chocolate banana surprise'
Ingredients
| id | name
| 1 | 'banana'
| 2 | 'cream'
| 3 | 'chocolate'
RecipeIngredients
| recipe_id | ingredient_id
| 1 | 2
| 1 | 3
| 2 | 1
| 2 | 2
| 3 | 1
| 3 | 3
如何构建 SQL 查询来查找配料.name = 'chocolate' 和配料.name = 'cream' 的食谱?
Given the following tables:
Recipes
| id | name
| 1 | 'chocolate cream pie'
| 2 | 'banana cream pie'
| 3 | 'chocolate banana surprise'
Ingredients
| id | name
| 1 | 'banana'
| 2 | 'cream'
| 3 | 'chocolate'
RecipeIngredients
| recipe_id | ingredient_id
| 1 | 2
| 1 | 3
| 2 | 1
| 2 | 2
| 3 | 1
| 3 | 3
How do I construct a SQL query to find recipes where ingredients.name = 'chocolate' and ingredients.name = 'cream'?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(6)
使用:
这里的关键点是计数必须等于成分名称的数量。如果不是重复计数,则存在由于重复而导致误报的风险。
Use:
The key point here is that the count must equal the number of ingredient names. If it's not a distinct count, there's a risk of false positives due to duplicates.
这称为关系划分。讨论了各种技术此处。
尚未给出的一种替代方案是双 NOT EXISTS
This is called relational division. A variety of techniques are discussed here.
One alternative not yet given is the double NOT EXISTS
如果您要搜索多个关联,那么编写查询的最简单方法是使用多个
EXISTS
条件,而不是单个直接的JOIN
。如果您确定关联是唯一的(即单个配方只能有每种成分的单个实例),那么您可以使用带有
COUNT
函数和速度的分组子查询来作弊(性能将取决于 DBMS):或者,如果一个配方可能有相同成分的多个实例(
RecipeIngredients
关联表上没有UNIQUE
约束),您可以将最后一行替换为:If you're searching for multiple associations then the simplest way to write the query is to use multiple
EXISTS
conditions instead of a single straightJOIN
.If you know for sure that the associations are unique (i.e. a single recipe can only have a single instance of each ingredient), then you can cheat a bit using a grouping subquery with a
COUNT
function and possibly speed it up (performance will depend on the DBMS):Or, if a recipe might have multiple instances of the same ingredient (no
UNIQUE
constraint on theRecipeIngredients
association table), you can replace the last line with:编辑了以下评论,谢谢!那么这是正确的方法:
Edited following comment, thanks! This is the right way then:
另一种方式:
版本 2(作为存储过程)修订
编辑 2:
[在人们开始尖叫之前]:)
这可以放在版本 2 的顶部,这将允许按名称查询而不是传入 id。
我已经测试了版本 2,它可以工作。大多数用户在成分表上进行链接,在这种情况下完全不需要!
编辑 3:(测试结果);
运行此存储过程时,这些是结果。
结果的格式为 (First Recipe_id ; Second Recipe_id, Result)
显然,此查询不处理两个约束相同的情况,但适用于所有其他情况。
编辑4:(处理相同的约束情况):
替换此行:
以
处理失败的情况以给出:
a different way:
Version 2 (as stored procedure) revised
Edit 2:
[before people start screaming] :)
This can be placed at the top of version 2, which will allow to query by name instead of passing in the id.
I've tested version 2, and it works. Most users where linking on the Ingredient table, in this case was totally not needed!
Edit 3: (test results);
When this stored procedure is run these are the results.
The results are of the format (First Recipe_id ; Second Recipe_id, Result)
Clearly this query does not handle case when both constraints are the same, but works for all other cases.
Edit 4:(handling same constraint case):
replacing this line:
to
works with the failed cases to give: