Improve error message for timestamp queries outside supported range

[Abdi-29]

Which issue does this PR close?

Closes #5581

Rationale for this change

This change improves the error message handling for timestamp queries outside the supported range in Datafusion. Currently, users receive confusing error messages about nanosecond overflow, which do not clearly explain the limitation of timestamp queries. This change enhances the user experience and reduces confusion by providing clearer guidance.

What changes are included in this PR?

This PR updates the error message handling for timestamp queries to provide clearer guidance when timestamps fall outside the supported range.

Are there any user-facing changes?

Users will receive more informative error messages when executing timestamp queries outside the supported range.

[Abdi-29]

Hi @tustvold,
do you know what the next step it's going to be?

[alamb]

Thank you @Abdi-29 -- this looks good to me ❤️ Nice work on the tests

I left a few comments, but I think we could merge this as is as well

Just let me know

[alamb]

I wonder if you would be willing to improve the messages for the other types (like Microsecond, etc)?

[Abdi-29]

Yes sure, I can work on it. Thanks for the feedback

[Abdi-29]

@alamb I did some research about the range of the other types but I couldn't find anything. Do you have any tips for me on where I can search for them?

[alamb]

I think you could create an array with T::Min of the underlying type

something like (untested):

let min_date = DateTimeArray::from(vec![i32::MIN, i32:MAX]));
pretty_print(min_date)

[Abdi-29]

thanks, I'll try it now

[alamb]

I tried

    let  a  = Arc::new(TimestampMicrosecondArray::from(vec![Some(i64::MIN), Some(i64::MAX)]));
    println!("{}", pretty_format_columns("foo", &[a]).unwrap());

And I got

+--------------------------------------------------------------------------------------------------------+
| foo                                                                                                    |
+--------------------------------------------------------------------------------------------------------+
| ERROR: Cast error: Failed to convert -9223372036854775808 to datetime for Timestamp(Microsecond, None) |
| ERROR: Cast error: Failed to convert 9223372036854775807 to datetime for Timestamp(Microsecond, None)  |
+--------------------------------------------------------------------------------------------------------+

So if you can figure out the min/max values that were allowed for that type and then that code would show you the string value I think

However, to be honest what we have in this PR is better than main, I think we could merge it as is

[Abdi-29]

Ah I see, thanks. I'll open another issue to fix this

[alamb]

Thanks for the effort @Abdi-29 -- I think this PR is better than what is on main, even though it could be improved for other types as well

Thanks again