Yes, this is wrong according to the program specification—that's not being slightly picky at all! It's a common error class that you need to watch out for because it can have real consequences, for example if you set about building a fence and find yourself one post short:

https://en.wikipedia.org/wiki/Off-by-one_error

int / int = int
5 / 4 = 1, not 1.250000

Im felling very dumby

I like how concise this is, but I'm not sure an order by col index is a best practice. Not that I don't also use it, but that's mostly when I'm in an RDBMS that won't let me reference a derived field by its alias. PostGres does allow it (ie: order by batting_average desc).

I need to get more accustomed to the ::casting operators in postgres. Oracle and SQLServer don't have them.

Why the CASE clause? It seems as in all cases, you return t1.str * t2.multiplier, serving no specific purpose.

Yes, you're completely right. Something should have been done first.

Shouldn't you have just-in-cased sL[i] in d as well then?

:) Just in Case..

Allowing for very clever speech recognition, that can hear Capitals .. :P