> OK, what's the reason then? I didn't hear you give one.
Read the rest of that paragraph. You only quoted the first sentence.
> Every PGSQL query already return multiple values because you get a command status along with the result set.
And most generic database driver interfaces (ex: JDBC) return that out of band. Errors get turned into exceptions and update counts get returned back as integers. That's far from perfect (particularly with JDBC) but it's usually done to fit the programming paradigms of the driver's native language.
> Every Golang call returns 2 values. They even make it very easy for you to return even more values. So what is your reasoning?
That's because Golang doesn't have exceptions. Every function that could fail needs to indicate if there's an error. It's like errno in C but per-function.
Read the rest of that paragraph. You only quoted the first sentence.
> Every PGSQL query already return multiple values because you get a command status along with the result set.
And most generic database driver interfaces (ex: JDBC) return that out of band. Errors get turned into exceptions and update counts get returned back as integers. That's far from perfect (particularly with JDBC) but it's usually done to fit the programming paradigms of the driver's native language.
> Every Golang call returns 2 values. They even make it very easy for you to return even more values. So what is your reasoning?
That's because Golang doesn't have exceptions. Every function that could fail needs to indicate if there's an error. It's like errno in C but per-function.