You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I reported in #3379, the query still succeeds and returns when an unsupported type is used, but an exception occurs when I use this object of the type I defined. In my opinion, the type should be checked and prompted at the time of use or startup.
The text was updated successfully, but these errors were encountered:
Guys I didn't understand that issue has opened #3379 in this is closed but here is registered as enhancement. Should I take to work on this issue
please see this url: #3379 (comment) , I think an enhancement is needed to make it easier to throw exceptions or print logs to note unsupported return types. It is not very friendly to throw an exception when the result is returned with the wrong type but only when used
As I reported in #3379, the query still succeeds and returns when an unsupported type is used, but an exception occurs when I use this object of the type I defined. In my opinion, the type should be checked and prompted at the time of use or startup.
The text was updated successfully, but these errors were encountered: