Skip to Content.
Sympa Menu

freetds - RE: [freetds] No tables displayed in StarOffice usinf FreeTDS/ODB C

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'freetds AT lists.ibiblio.org'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] No tables displayed in StarOffice usinf FreeTDS/ODB C
  • Date: Wed, 18 Dec 2002 14:36:04 -0500

> From: Martin Spott [mailto:mas AT plesnik.de]
> Sent: December 18, 2002 10:22 AM
>
> odbc:SQLGetInfo: info option 25 not supported
> odbc:SQLGetInfo: info option 86 not supported
>
> Does anyone have a clue how these messages have to be interpreted ?

I parsed the documentation and header files, loaded them into tables, and
got the following:

1> select InfoTypeCategory, InfoType, Value from OdbcParameters p join
OdbcConstants c on InfoType = Symbol where Value in (25,86)
2> go
InfoTypeCategory InfoType Value
------------------------ ------------------------- -----
Data Source Information SQL_DATA_SOURCE_READ_ONLY 25
Supported SQL SQL_ALTER_TABLE 86

If others think this sort of thing is useful, I'll add the data files and
DDL to cvs. Where would we put such data? doc/symbols/odbc?

What I have:

* text files based on SQLGetInfo documentation
* perl to parse those files
* tab-delimited metadata files (perl output)

I think querying tables is easier than scanning header files, and data files
are tractable when trying to create documentation or giant switch
statements.

--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