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

RE: ODBC driver (SQLGetTypeInfo)

From: Paul Lisewski <paull(at)techone(dot)com(dot)au>
To: "'Byron Nikolaidis'" <byronn(at)insightdist(dot)com>, Paul Lisewski <paull(at)techone(dot)com(dot)au>, pgsql-interfaces <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: RE: ODBC driver (SQLGetTypeInfo)
Date: 1998-04-20 02:06:06
Message-ID: 5ABEF3A77B39D111970F0020AFA04D29AE26@mailbox.techone.com.au (view raw or flat)
Thread:
Lists: pgsql-interfaces
Terrific,
	Just what I was after.

Thanks very much.

Regards,

Paul Lisewski,
(paull(at)techone(dot)com(dot)au)

> -----Original Message-----
> From:	Byron Nikolaidis [SMTP:byronn(at)insightdist(dot)com]
> Sent:	18 April 1998 6:33
> To:	Paul Lisewski; pgsql-interfaces
> Subject:	Re: ODBC driver (SQLGetTypeInfo)
> 
> Paul,
> 
> I changed the driver to handle this a little better.
> 
> - text was already SQL_LONGVARCHAR.
> - name is now SQL_CHAR (fixed at 32) - it should have been this all
> along
> - varchar and bpchar both return SQL_VARCHAR, BUT varchar now comes
> first,
> since it is most correct anyway, I think that makes sense.
> 
> Hope this helps.
> 
> The latest stuff is at our web site.
> 
> Byron
> 
> 
> Paul Lisewski wrote:
> 
> > When getting a list of DataTypes via SQLGetInfo, there are 4
> SQL_VARCHAR
> > types.
> > They are:
> > bpchar, varchar, text and name.
> >
> > I have a utility to interogate a database and create tables using
> the
> > syntax from SQLGetInfo. I pick the first match from the list (in
> this
> > case bpchar). Could the Types be modified to SQL_LONGVARCHAR for the
> non
> > varchar datatypes or at least resequenced so that varchar comes
> before
> > bpchar
> >
> > Various version of PostODBC used to have this problem, then it was
> > changed so that bpchar reported SQL_LONGVARCHAR.
> >
> 
> 

pgsql-interfaces by date

Next:From: Aleksey DemakovDate: 1998-04-20 06:22:09
Subject: Re: [INTERFACES] Re: ODBC driver and Dates
Previous:From: Paul LisewskiDate: 1998-04-20 01:57:24
Subject: RE: ODBC driver

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