Re: [I] Cannot use null values as bound parameters in postgresql [arrow-adbc]

["lidavidm (via GitHub)" <gi...@apache.org>]

lidavidm commented on issue #3549:
URL: https://github.com/apache/arrow-adbc/issues/3549#issuecomment-3782069484

   @Mandukhai-Alimaa are you interested at looking at this one? I think this requires some planning: I think what needs to happen here is that when binding parameters, we should first get Postgres's expected parameter types, then try to reconcile with that. For example, if the parameter has type INT but the Arrow array has type NA, we should bind null values of type INT. 
   
   There are complications: I think Postgres reports that the parameter is type string when it doesn't know or when there are multiple possibilities (`SELECT $1`). We shouldn't cause errors in this case. So maybe the best thing is to hardcode an "upcast" of NA arrays to Postgres's expected parameter type, but otherwise ignore mismatches.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org