Well since there is no CREATE PROCEDURE in postgresql, it becomes
somewhat redundant to have getFunctions and getProcedures. Ironically
we support getProcedures only because it was in the API first.
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On Mon, Sep 24, 2012 at 1:49 PM, the6campbells <the6campbells@gmail.com> wrote:
> Semantically, one would hope that the advertised method is used to get an
> object of the type (procedure vs function) vs using an overloaded method
> which conceptually is returning both. Perhaps PG may internally treat both
> objects as the same type but you'd like to think that one could say create
> procedure and create function and be able locate said via canonical API
> method such as DatabaseMetadata.get<xxyyzz>
>
>
> On Mon, Sep 24, 2012 at 1:35 PM, Dave Cramer <pg@fastcrypt.com> wrote:
>>
>> This is just an alias for getProcedures, so 1) it's probably fairly
>> easy to implement and 2) why not just use getProcedures ?
>> Dave Cramer
>>
>> dave.cramer(at)credativ(dot)ca
>> http://www.credativ.ca
>>
>>
>> On Mon, Sep 24, 2012 at 12:59 PM, the6campbells <the6campbells@gmail.com>
>> wrote:
>> > Currently fails
>> >
>> > PostgreSQL 9.1 JDBC4 (build 902)
>> > 9.0.4
>> >
>> > Error calling JDBC driver for procedure metadata.
>> > org.postgresql.Driver.notImplemented(Driver.java:751)
>> >
>> > org.postgresql.jdbc4.AbstractJdbc4DatabaseMetaData.getFunctions(AbstractJdbc4DatabaseMetaData.java:82)
>> > SQLException.sqlState(0A000) SQLException.Message(Method
>> > org.postgresql.jdbc4.Jdbc4DatabaseMetaData.getFunction(String, String,
>> > String) is not yet implemented.)
>> >
>
>
