Any plans to support SQLDescribeParam (and friends) ?

--=-BSDv8i92O9oq6KSqjyIF
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi

Previously PsqlODBC did not support SQLDescribeParam (and friends), as
the PostgreSQL backend/frontend protocol did not offer the necessary
support to implement these functions [1]. Or at least, that is how I
understand it.

But with protocol version 3, it should be possible to implement
SQLDescribeParam[2].

Thus my question, is there any plans to support SQLDescribeParam (and
friends) ?


Regards,

Mads Lindstrøm


[1] http://library.pantek.com/Mailing%
20Lists/postgresql.org/pgsql-interfaces/03/03/11602.html

[2]
http://www.postgresql.org/docs/8.4/interactive/libpq-exec.ht ml#LIBPQ-EXEC-S=
ELECT-INFO search for PQnparams, PQparamtype


--=-BSDv8i92O9oq6KSqjyIF
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkpaHT8ACgkQJPQyo1ZQv/bFUgCeKxpM+k7QudTAgj5/1gN1 o7ZX
XNwAoJlibwckubwqqNd1YtLjzFqpWpBL
=zhNM
-----END PGP SIGNATURE-----

--=-BSDv8i92O9oq6KSqjyIF--

Re: Any plans to support SQLDescribeParam (and friends) ?

Mads Lindstrøm wrote:
> Hi
>=20
> Previously PsqlODBC did not support SQLDescribeParam (and friends), as
> the PostgreSQL backend/frontend protocol did not offer the necessary
> support to implement these functions [1]. Or at least, that is how I
> understand it.
>=20
> But with protocol version 3, it should be possible to implement
> SQLDescribeParam[2].
>=20
> Thus my question, is there any plans to support SQLDescribeParam (and
> friends) ?

You can call SQLDescribeParam() with the current driver when you
check the 7.4+ Protocol option and the Server side prepare option.

regards,
Hiroshi Inoue



--=20
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: Any plans to support SQLDescribeParam (and friends) ?

--=-0Zj9UDiOS075JV5lt3uM
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Hiroshi,

Thank you for the reply.


Hiroshi Inoue wrote:

> Mads Lindstrøm wrote:
> > Hi
> >=20
> > Previously PsqlODBC did not support SQLDescribeParam (and friends), as
> > the PostgreSQL backend/frontend protocol did not offer the necessary
> > support to implement these functions [1]. Or at least, that is how I
> > understand it.
> >=20
> > But with protocol version 3, it should be possible to implement
> > SQLDescribeParam[2].
> >=20
> > Thus my question, is there any plans to support SQLDescribeParam (and
> > friends) ?
>=20
> You can call SQLDescribeParam() with the current driver when you
> check the 7.4+ Protocol option and the Server side prepare option.
>=20
> regards,
> Hiroshi Inoue
>=20

Yes, I can call SQLDescribeParam(..), but it always return VarChar, on
SMALLINT, INTEGER, BIGINT and DECIMAL parameters. So I guess I am doing
something wrong.

My odbc.ini looks like:

[MetaHDBC_PQ_DSN]
Description =3D PostgreSQL ODBC
Driver =3D postgreodbc
Trace =3D No
TraceFile =3D
Database =3D MetaHDBC_DB
Servername =3D localhost
UserName =3D metahdbc
Password =3D foobar
Port =3D 5432
Protocol =3D 8.3
ReadOnly =3D No
RowVersioning =3D No
ShowSystemTables =3D No
ShowOidColumn =3D No
FakeOidIndex =3D No
ConnSettings =3D
#ServerSidePrepare =3D Yes
UseServerSidePrepare =3D Yes

And the odbcinst.ini looks like:

[postgreodbc]
Description =3D PostgreSQL ODBC driver
Driver =3D /usr/lib/odbc/psqlodbcw.so
#Setup =3D /usr/lib/odbc/libodbcpsqlS.so
Debug =3D 0
CommLog =3D 1
UsageCount =3D 2


Do anybody have an idea of why I only see VarChar when calling
SQLDescribeParam(..) ?

Or any pointers to how I can debug the problem.

I am running on Debian Linux (Lenny) using psqlodbc version
(1:08.03.0200-1) (see
http://packages.debian.org/source/lenny/psqlodbc ).


Regards,

Mads Lindstrøm



--=-0Zj9UDiOS075JV5lt3uM
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkph/sYACgkQJPQyo1ZQv/aEmACgh0AEOO2162emN5uYyiTK X8Hv
pYwAn1PYaFF+cKiuu71yqqDVgOMMA7bD
=tcQz
-----END PGP SIGNATURE-----

--=-0Zj9UDiOS075JV5lt3uM--

Re: Any plans to support SQLDescribeParam (and friends) ?

Hi Mads,

Mads Lindstrøm wrote:
> Hi Hiroshi,
>=20
> Thank you for the reply.
>=20
>=20
> Hiroshi Inoue wrote:
>=20
>> Mads Lindstrøm wrote:
>>> Hi
>>>
>>> Previously PsqlODBC did not support SQLDescribeParam (and friends), a=
s
>>> the PostgreSQL backend/frontend protocol did not offer the necessary
>>> support to implement these functions [1]. Or at least, that is how I
>>> understand it.
>>>
>>> But with protocol version 3, it should be possible to implement
>>> SQLDescribeParam[2].
>>>
>>> Thus my question, is there any plans to support SQLDescribeParam (and
>>> friends) ?
>> You can call SQLDescribeParam() with the current driver when you
>> check the 7.4+ Protocol option and the Server side prepare option.
>>
>> regards,
>> Hiroshi Inoue
>>
>=20
> Yes, I can call SQLDescribeParam(..), but it always return VarChar, on
> SMALLINT, INTEGER, BIGINT and DECIMAL parameters. So I guess I am doing
> something wrong.
>=20
> My odbc.ini looks like:
>=20
> [MetaHDBC_PQ_DSN]
> Description =3D PostgreSQL ODBC
> Driver =3D postgreodbc
> Trace =3D No
> TraceFile =3D
> Database =3D MetaHDBC_DB
> Servername =3D localhost
> UserName =3D metahdbc
> Password =3D foobar
> Port =3D 5432
> Protocol =3D 8.3

Could you try to set
Protocol =3D 7.4
?

regards,
Hiroshi Inoue

--=20
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: Any plans to support SQLDescribeParam (and friends) ?

--=-jbDGJOt8mKroMKm3LWex
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi Hiroshi,

Hiroshi Inoue wrote:
> >> You can call SQLDescribeParam() with the current driver when you
> >> check the 7.4+ Protocol option and the Server side prepare option.
> >>
> >> regards,
> >> Hiroshi Inoue
> >>
> >=20
> > Yes, I can call SQLDescribeParam(..), but it always return VarChar, on
> > SMALLINT, INTEGER, BIGINT and DECIMAL parameters. So I guess I am doing
> > something wrong.
> >=20
> > My odbc.ini looks like:
> >=20
> > [MetaHDBC_PQ_DSN]
> > Description =3D PostgreSQL ODBC
> > Driver =3D postgreodbc
> > Trace =3D No
> > TraceFile =3D
> > Database =3D MetaHDBC_DB
> > Servername =3D localhost
> > UserName =3D metahdbc
> > Password =3D foobar
> > Port =3D 5432
> > Protocol =3D 8.3
>=20
> Could you try to set
> Protocol =3D 7.4
> ?
>=20
> regards,
> Hiroshi Inoue
>=20

Same results with Protocol =3D 7.4


Regards,

Mads

--=-jbDGJOt8mKroMKm3LWex
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkpituYACgkQJPQyo1ZQv/YnZACdHM9+PSi7fjjG41ZnorOq jT9v
0PQAoKr0cCWqG3h5M1zfUZuwWk5/Ss2C
=Z++7
-----END PGP SIGNATURE-----

--=-jbDGJOt8mKroMKm3LWex--