Re: check whether a relationship is empty, efficiently
Re: check whether a relationship is empty, efficiently
- Subject: Re: check whether a relationship is empty, efficiently
- From: Theodore Petrosky <email@hidden>
- Date: Wed, 03 Feb 2016 22:10:05 -0500
but what about raw SQL? Instead of talking to the EO.
Of course my methods always end up convoluted but I thought about putting a method on the EO that uses raw SQL to return the count of related objects.
> On Feb 3, 2016, at 8:34 PM, OC <email@hidden> wrote:
>
> Hello there,
>
> I'd bet this must be a WebObjects 101, but I can't see the best answer: is there an efficient way of checking whether an eo.someRelationship is empty?
>
> So far I simply check eo.someRelationship.count==0, but that might fire a fault, which is not exactly efficient if the only need is to know whether the relationship is empty or not.
>
> Of course I could rig myself something like “if already fetched in, simply check array count; if still fault, fetch max one object and see whether there's any...”, but this looks like a ubiquitous task enough it simply _must_ be done already (and in a far better way than I would do it myself)?
>
> Thanks for any advice,
> OC
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden