Stefan is right, “containsAnyObjectSatisfying” will create an Exists qualifier using EOExistsQualifier.
If you don’t want to create the “User.ORGANIZATIONS” back relationship… then create a “User2” EO where you model it. Use that doppelgänger EO to do your qualifier. You can then convert individual User2 objects to User1 with a toOne relationship on Primary Key… or simply add the fields you want to User2 to display. > On Oct 7, 2025, at 4:36 AM, Paul Hoadley via Webobjects-dev > <[email protected]> wrote: > > Thanks Stefan. Yeah, I think that's what is going to prevent this—there is no > inverse relationship. > > > On 7 Oct 2025, at 4:02 pm, Stefan Gärtner <[email protected]> wrote: > >> Hello Paul, >> >> if User had a to-many relationship to Organization (the inverse of >> complianceOfficer), you could use: >> >> User.ORGANISATIONS.containsAnyObjectSatisfying(new ERXTrueQualifier()) >> >> Best regards, >> Stefan > > > -- > Paul Hoadley > https://logicsquad.net/ > https://www.linkedin.com/company/logic-squad/ > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/aaron%40chatnbike.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
