JPA/JPQL中member-of使用问题及@ManyToMany列表查询替代方案

Hey there! Let's work through your problem with checking if an element exists in a @ManyToMany list using JPA/JPQL.

First: Correcting the MEMBER OF Parameter Usage #

It looks like your parameter handling syntax (parameter.get("" i + anlass)) has a typo—you're mixing up string concatenation and parameter naming. Here's how to properly use MEMBER OF with your Rezept and Allergie entities:

Step 1: Write the Correct JPQL Query #

Your entity has a List<Allergie> allergien mapped as @ManyToMany, so the JPQL to check if a specific Allergie is in that list would be:

SELECT r FROM Rezept r WHERE :targetAllergie MEMBER OF r.allergien

Step 2: Set the Parameter Properly in Java #

When executing this query, pass the actual Allergie instance as a named parameter (no messy string concatenation needed):

// Assuming you have an EntityManager instance named em
Allergie targetAllergie = // your Allergie instance to check
TypedQuery<Rezept> query = em.createQuery(
    "SELECT r FROM Rezept r WHERE :targetAllergie MEMBER OF r.allergien",
    Rezept.class
);
query.setParameter("targetAllergie", targetAllergie);
List<Rezept> matchingRezepte = query.getResultList();

The key here is using a named parameter (like :targetAllergie) that matches exactly what you pass to setParameter()—no dynamic string hacks that cause syntax errors.

Alternative Ways to Check for @ManyToMany Membership #

If you want alternatives to MEMBER OF, here are two reliable approaches:

1. Use a JOIN #

This is straightforward and often performs well, especially if you need to fetch additional related data:

SELECT r FROM Rezept r JOIN r.allergien a WHERE a = :targetAllergie

The Java parameter setup is identical to the MEMBER OF example above.

2. Use an EXISTS Subquery #

Great for more complex scenarios where you need additional filters in the subquery:

SELECT r FROM Rezept r 
WHERE EXISTS (
    SELECT 1 FROM r.allergien a 
    WHERE a = :targetAllergie
)

This checks for the existence of the target Allergie in the Rezept's list without joining the entire collection.

Quick Note on Your Entity Mapping #

Just a quick sanity check: your @ManyToMany(mappedBy="rezepten") on Rezept.allergien means the owning side is on the Allergie entity (with a field named rezepten). That's totally fine, but make sure both sides are properly synchronized if you're modifying the collection (though that's unrelated to your current query issue).

内容的提问来源于stack exchange，提问作者Alina