On 2017/02/04 9:54, Vilches, Alejandro wrote:
> It's actually without time zone. However, it doesn't seem like ODBC allows me to specify that. When I bind the
parameter,I can only say: SQL_TYPE_TIMESTAMP.
Hmm the current FE/BE protocol doesn't allow to specify preferable
parameter type(oid) unfortunately.
Probably I can make a patch to use unknown parameters instead of
specifying parameters by oid.
Could you test it?
regards,
Hiroshi Inoue
>
> -----Original Message-----
> From: Inoue, Hiroshi [mailto:h-inoue@dream.email.ne.jp]
> Sent: Friday, February 3, 2017 4:45 PM
> To: Vilches, Alejandro <alejandro.vilches@intel.com>; Adrian Klaver <adrian.klaver@aklaver.com>
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Problem calling a function from ODBC application
>
> Hi,
>
> On 2017/02/04 9:31, Vilches, Alejandro wrote:
>> Oh goodness, that's embarrassing :).
>>
>> Okay, so I've tried the following:
>>
>> - I fixed the small sample program and now that one executes successfully
>>
>> - I created another sample program that calls a stored function with the same number of parameters and types as the
onein my real application and now that fails with the following error message (the same error message I originally
reported):
>> ERROR: function my_function3(bigint, bigint, integer, integer, timestamp with time zone, integer, integer, integer,
integer,integer, integer, unknown, unknown) does not exist;
> Is the type of parameter 'timestamp with time zone' right?
>
>> Error while preparing parameters
>>
>> I've attached the new sample program. The stored function can be any dummy function.
>>
>> Thanks!
>> Alejandro