Re: Fwd: [JDBC] Weird issues when reading UDT from stored function - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Fwd: [JDBC] Weird issues when reading UDT from stored function
Date
Msg-id AANLkTinTObZFcafnujUAxyPM3+ZHbP+qZb+QMnLE=Zuv@mail.gmail.com
Whole thread Raw
In response to Re: Fwd: [JDBC] Weird issues when reading UDT from stored function  (Florian Pflug <fgp@phlo.org>)
Responses Re: Fwd: [JDBC] Weird issues when reading UDT from stored function  (rsmogura <rsmogura@softperience.eu>)
List pgsql-hackers
2011/2/17 Florian Pflug <fgp@phlo.org>:
> On Feb17, 2011, at 10:30 , rsmogura wrote:
>> When JDBC driver will detect if procedure call statement is created.
>> 1. Determine procedure oid - how? procedures may have not qualified name. Is any function on backend that will deal
withschema search path? You may need to pass procedure parameters or at least types? or we need to mirror backend code
toJava? 
>
> That change of getting this correct without help from the backend is exactly zero. (Hint: You need to consider
overloadedfunctions and implicit casts of parameters...) 
>

There is only one way - implementation of CALL statement. Any
emulation on JDBC level is just way to hell. Now, we have to say -
PostgreSQL doesn't support a CALL statement, support only functions -
and everybody has to use a different pattern than in other databases.
Any emulation on JDBC means, it will be slowly, it will be
unpredictable.

Regards

Pavel Stehule


> best regards,
> Florian Pflug
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: Fwd: [JDBC] Weird issues when reading UDT from stored function
Next
From: Andrea Suisani
Date:
Subject: Re: Debian readline/libedit breakage