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(33292)
}
}
If teams around the league believe that Melo really wants out, then its going to be tough to get value back. Personally, I'd be surprised if Melo went so far as to opt out of the $23mill option he has for next season, so if I were the Knicks I wouldn't hit the panic button for awhile yet.
They might get some interesting offers if they were willing to blow it up and take back picks/ expiring deals.
They aren't getting Blake Griffin for him though! Clippers have him under contract for several years at a much more reasonable price than Melo's $23mill per.
1) Get rid of him and get something for him, rather than him walking in FA. Downside of this is that you inherit salary/acquire someone on the books
2) Wait until he walks in FA. Seems like a huge loss for the Knicks as they essentially get nothing for him. But the advantage is that you clear a huge amount of the cap and can then rebuild from scratch with cap space.