Skip site navigation (1) Skip section navigation (2)

Re: Simple Q: Does the ODBC driver support LONGVARCHAR?

From: "Byron Nikolaidis" <byron(dot)nikolaidis(at)home(dot)com>
To: "Adam Rossi" <adam(dot)rossi(at)platinumsolutions(dot)com>, <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: Simple Q: Does the ODBC driver support LONGVARCHAR?
Date: 2000-06-19 23:18:54
Message-ID: 000b01bfda44$bcc93f00$6401a8c0@byron (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
You are supposed to query odbc for the "native" data type names and then use
that in your Create Table statement.   Use the SQLGetTypeInfo() call -- the
TYPE_NAME field is what you want.   You can pass either the specific type
(SQL_LONGVARCHAR) or SQL_ALL_TYPES to get all of them at once.

Quoting from the odbc spec about SQLGetTypeInfo()... TYPE_NAME:  Data
Source-Dependent data type name... Applications must use this name in CREATE
TABLE and ALTER TABLE statements.


----- Original Message -----
From: Adam Rossi <adam(dot)rossi(at)platinumsolutions(dot)com>
To: <pgsql-interfaces(at)postgresql(dot)org>
Sent: Monday, June 19, 2000 3:26 PM
Subject: [INTERFACES] Simple Q: Does the ODBC driver support LONGVARCHAR?

> Does the ODBC driver support longvarchar? It seems that no matter what I
> with the settings for the driver, such as checking "Unknowns as
> LongVarChar", "Text as LongVarChar", "Parse Statements", etc., the
> longvarchar type NEVER works. In this simple SQL statement:
> create table test_table
>  testid INTEGER,
>  text_field LONGVARCHAR,
>  var_field VARCHAR(250),
>  char_field CHAR(1))
> the field "text_field" defined as type "LONGVARCHAR" will always cause the
> statement to fail with the following message:
> ERROR:  Unable to locate type name 'longvarchar' in catalog' (#17)
> If I change the "LONGVARCHAR" to "TEXT", the statement below works fine:
> create table test_table
>  testid INTEGER,
>  text_field TEXT,
>  var_field VARCHAR(250),
>  char_field CHAR(1))
> Since I am relying on some builder tools that only support ODBC standard
> types (i.e. LONGVARCHAR and not TEXT), it would make my life a lot easier
> I could get LONGVARCHAR to work. Is this some deficiency in the driver?
> Shouldn't an ODBC driver support the major ODBC types? Could anyone point
> in the right direction to hack the driver if it currently does not support
> this syntax?
> Thanks for your help.
> - Adam

In response to

pgsql-interfaces by date

Next:From: Bob KlineDate: 2000-06-20 10:25:15
Subject: getMoreResults() returns false incorrectly
Previous:From: John CampbellDate: 2000-06-19 19:54:08
Subject: pgacess deletes function in database

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group