array(2) {
[0]=>
string(815) "
select r.*,
rc.info,
t.title as threadtitle,
u.username as username,
u.anonymous as useranonymous,
`f`.`value` AS `flairvalue`,
`ft`.`name` AS `flairname`,
`ft`.`colour` AS `flaircolour`,
`ft`.`icon` AS `flairicon`
from reply as r
join thread as t on t.id = r.threadid
join replycontent as rc on rc.replyid = r.id
join user as u on u.id = r.userid
left join `flair` `f` on `f`.`userid` = `u`.`id` and `f`.`categoryid` = `t`.`categoryid`
left join `flairoption` `ft` on `ft`.`id` = `f`.`flairoptionid`
where r.businessid = :businessId
and r.threadid = :threadId
group by r.id
order by r.utcdated desc
limit 0,50
"
[1]=>
array(2) {
["businessId"]=>
int(1)
["threadId"]=>
int(33370)
}
}

Years ago
NBL stats...points in the paint and fast break pts
Points in the paint should be OK as that is automatically derived from where the Statistician clicks the mouse to indicate where on the court the shot was taken.
But while recent versions of FIBA LiveStats (the program used to collect the stats for almost all leagues in Australia) has the ability to record fastbreak points, the official Australian calling protocol has not been updated to define how it is to be used. Thus you get inconsistent use of it and I would say invariably low captured numbers. Hopefully BA's Stats Committee will update the aclling protocol soon.

Years ago
There is your answer, get the stats relevant to something associated with gambling or betting and it will be done brilliantly!
Problem solved...
