RE: ODBC driver (SQLGetTypeInfo)
От | Paul Lisewski |
---|---|
Тема | RE: ODBC driver (SQLGetTypeInfo) |
Дата | |
Msg-id | 5ABEF3A77B39D111970F0020AFA04D29AE26@mailbox.techone.com.au обсуждение исходный текст |
Список | pgsql-interfaces |
Terrific, Just what I was after. Thanks very much. Regards, Paul Lisewski, (paull@techone.com.au) > -----Original Message----- > From: Byron Nikolaidis [SMTP:byronn@insightdist.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 по дате отправления: