On Wed, 6 Oct 2004, Oliver Jowett wrote:
> It seems possible to fix the driver to handle this case by making
> setArray() derive a proper array type name i.e. ("_" +
> Array.getBaseType()), and using that rather than 'text' as the parameter
> type.
>
Wouldn't it be simpler to change setArray to call setString with 0 as the
type oid allowing the backend to figure out what to do with it? Perhaps
it would have trouble determining the type if the underlying function was
overloaded, but other than that I don't see a problem.
Kris Jurka
