[eluser]nevsie[/eluser]
i would have thought you would actually like to count anything under par for this...
But depending upon how you caching this i think you are maybe going about this a little backward. Everytime someone runs this query a bugger load of processing will need to be done - whereas if you calculate how many birdies someone has had when they enter the score, you only process it the once, and can store that value in a field ready to access... This might be as a value, or as a birdy flag (1/0) or maybe a shot count (-3,-2,-1,0,1,2,3,4,5,6,etc).
Then you just query the number of shots of -1 or below, group them by member id and meeting id (accumulating the result and use that...
You can do it your way, and it might be possible to do this with lower overheads than i am currently thinking of, but this seems a good alternative direction to me.