Skip to Content.
Sympa Menu

freetds - RE: [freetds] FreeTDS, unixODBC, and libodbc++

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'Joel Apter' <japter AT ibxtech.com>, 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Cc:
  • Subject: RE: [freetds] FreeTDS, unixODBC, and libodbc++
  • Date: Thu, 12 Jun 2003 14:36:37 -0400

> From: Joel Apter [mailto:japter AT ibxtech.com]
> Sent: June 12, 2003 12:42 PM
>
> Error setting pointer statement option:
> [unixODBC][Driver Manager]Invalid attribute/option identifier
...
> odbc:SQLColAttributes: fDescType is 4
> odbc:SQLColAttributes: fDescType is 5
> odbc:SQLColAttributes: fDescType 5 not catered for...
^^^^^^^^^^^ clue
> odbc:SQLColAttributes: fDescType is 3
>
> I'm not sure if this means anything. What I am wondering is,
> is this an issue with freetds, unixodbc, or libodbc++ (or all
> of them, or none??)? Has anyone actually written a c++
> application usually a similar driver/driver manager setup?

Hi Joel,

We don't get a lot of libodbc++ questions, and I'm not sure anyone's gotten
it more than minimally working. OTOH, Frediano keeps making our ODBC driver
better and better. It tends to squawk when asked to do something it can't
yet do.

The "not catered" message comes from src/odbc/odbc.c::SQLColAttributes
(superseded by SQLColAttribute in the ODBC docs, btw). I think fDescType 5
might be SQL_COLUMN_SCALE, which we don't support. If that's the issue,
something like this might help:

case SQL_COLUMN_SCALE:
switch (colinfo->column_type) {
case SYBNUMERIC:
case SYBDECIMAL:
*pfDesc = colinfo->column_scale;
break;
default:
*pfDesc = 0;
break;
}
break;

Could you see if that at least doesn't make the log message go away?

Do the libodbc++ tests report anything interesting? Perhaps they have finer
grained checking of the underlying library that would help us flush out
what's missing.

What does unixODBC say about their message? Is there a way to get more (ie,
any) details? As in, say, which identifier was invalid, and what its value
was?

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page