Consider making the invalid input error message more descriptive

[koote]

What happened here is that the table expects an array of length 3, but the input array has length 2.
However, the current error message is too vague: "invalid input: expected 3, got 2".
It’s unclear what the numbers 3 and 2 refer to.

[taniabogatsch]

It looks like you addressed this in #91? Or am I missing something?

[koote]

It looks like you addressed this in #91? Or am I missing something?

No I didn't. The PR#91 is for adding a new error when SetValue fails.
I am not sure what is the coding standard of this project, is it recommended to format a string in function like:

	if len(array) != int(vec.arrayLength) {
		return invalidInputError("array of lengh " + strconv.Itoa(len(array)), "array of lengh " + strconv.Itoa(int(vec.arrayLength)))
	}

[taniabogatsch]

We usually use fmt.Sprintf to format strings.

[koote]

We usually use fmt.Sprintf to format strings.

I am new to this codebase so I am cautious about using fmt.Sprintf in this repo, as DuckDB aims to be high performance database and fmt.Sprintf involves interface boxing and reflection internally which could have a performance impact if it is used on hot path.

[taniabogatsch]

Hmm - how would the error message end up in a hot path? Isn't is a bug / interface error that should be fixed on the client-side?