| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | rsmogura <rsmogura(at)softperience(dot)eu> |
| Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Lukas Eder <lukas(dot)eder(at)gmail(dot)com>, <pgsql-jdbc(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
| Date: | 2011-02-17 09:39:17 |
| Message-ID: | 59E6DD07-0A30-498C-976C-04FA2DE2E290@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
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 with schema search path? You may need to pass procedure parameters or at least types? or we need to mirror backend code to Java?
That change of getting this correct without help from the backend is exactly zero. (Hint: You need to consider overloaded functions and implicit casts of parameters...)
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Eder | 2011-02-17 09:45:06 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
| Previous Message | Florian Pflug | 2011-02-17 09:33:11 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Eder | 2011-02-17 09:45:06 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
| Previous Message | Florian Pflug | 2011-02-17 09:33:11 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |