In this context, it may be a bad selection of name but I don't think it is broken. It is intended to be used on unique composite key(most likely cluster index). In a straight SQL sense, all results must be assumed to be multi rows and the SQLObject's .get() and byForeignKey() is also broken.
pierrebai wrote: > Yes, but your by() method was "broken" in the sense that it assumed > that there would be exactly one result, not 0, 2 or more. A dangerous > assumption.
