Wow! Thanks for pointing me back to Igor's example. It is, as you say, very slick. So slick, in fact, I missed it on first read, and assumed it wouldn't satisfy both requirements. My humble apology to Igor :-))
I must admit, after reading the sum(is_complete) suggestion, it was like the coconut falling on my head - a big "DUH!" moment. I still can't figure out why I didn't see it myself before asking. That's the real value of a great community like this one. -Clark ----- Original Message ---- From: Dennis Cote <[EMAIL PROTECTED]> To: sqlite-users@sqlite.org Sent: Tuesday, April 3, 2007 3:07:44 PM Subject: Re: [sqlite] SQL help Clark Christensen wrote: > > Yeah, that's much cleaner. Just once through the tech's module set instead > of twice, and it satisfies both requirements (at least some modules, and all > complete). > > Thanks again! > > Clark, You are welcome. You should probably look at Igor's idea though. It will eliminate the comparisons in your application code and return the allComplete value directly from the query. It's really very slick. Dennis Cote ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
