pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: ODBC driver (SQLGetTypeInfo)
2+ messages / 2 participants
[nested] [flat]
* Re: ODBC driver (SQLGetTypeInfo)
@ 1998-04-17 20:33 Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 0 replies; 2+ messages in thread
From: Byron Nikolaidis @ 1998-04-17 20:33 UTC (permalink / raw)
To: Paul Lisewski <paull@techone.com.au>; pgsql-interfaces
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.
>
^ permalink raw reply [nested|flat] 2+ messages in thread
* RE: ODBC driver (SQLGetTypeInfo)
@ 1998-04-20 02:06 Paul Lisewski <paull@techone.com.au>
0 siblings, 0 replies; 2+ messages in thread
From: Paul Lisewski @ 1998-04-20 02:06 UTC (permalink / raw)
To: 'Byron Nikolaidis' <byronn@insightdist.com>; Paul Lisewski <paull@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.
> >
>
>
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1998-04-20 02:06 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-04-17 20:33 Re: ODBC driver (SQLGetTypeInfo) Byron Nikolaidis <byronn@insightdist.com>
1998-04-20 02:06 RE: ODBC driver (SQLGetTypeInfo) Paul Lisewski <paull@techone.com.au>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox