> > The motivation is to come closer
> > to Oracle's SELECT INTO behavior: when SELECTing INTO scalar targets,
> > raise an exception and leave the targets untouched if the query does not
> > return exactly one row.
> why that is not the default behavior of the SELECT INTO?
> ...
> i mean, when you do that code you are expecting just one row from your
> query
I agree. I suppose I was fearful of breaking existing stuff, so I added
a new keyword.