From: Dario Fumagalli <dfumagalli@art-media.it>
To: Byron Nikolaidis <byronn@insightdist.com>
Cc: PostgreSQL interfaces mailing list <pgsql-interfaces@postgreSQL.org>
Subject: R: ODBC + Delphi (GREAT!) + some little thing//
Date: Fri, 24 Apr 1998 11:33:23 +0200
Message-ID: <199804240931.LAA08562@mail.art-media.it> (raw)
NOW THE QUERIES WORK!!!!!!!!!!!!!!!!!!!
Tank you. Now in my office there is the "Linux + PostgreSQL II - The
revenge"!
Seeing the lightning speed of the queries my pro-Windows NT colleagues are
embarassed!
Even the duplicate table name problem is gone.
I also tested some inserts and updates and they seem to work OK. My
programs started to work again...
For the new readers of this mailing list: the kind of support I have
received from the PostgreSQL guys, and in particular by Byron Nikolaidis is
invaluable. Their support quality and patience are at least an order of
magnitude better than any good commercial support I have seen.
Keep on the good work.
My very best regards,
Dario Fumagalli
email dfumagalli@art-media.it
----------
Da: Byron Nikolaidis <byronn@insightdist.com>
A: Zsolt Varga <redax@agria.hu>; dfumagalli@art-media.it; pgsql-interfaces
<pgsql-interfaces@postgreSQL.org>; hackers@postgreSQL.org
Oggetto: Re: ODBC + Delphi (GREAT!) + some little thing//
Data: venerdì 24 aprile 1998 5.35
Zsolt Varga wrote:
> On Thu, 23 Apr 1998, Byron Nikolaidis wrote:
>
> some little thing...
> from delphi I see the following Postgres types as:
> ---------------------------------------------
> bool --> char(2)
Bool is being handled as character data, so the 2 includes the null
terminator.This was under debate for a while. Handling it as a real
SQL_BOOL didn't seem to work well under Access so thats why it is char.
I could probably fix this now.
> varchar(x) x > 255 --> varchar(255)
Varchar's are limited in the driver to 255 to allow MS Access to be able
to index on these fields. Same with char(x).
> text -- > longvarchar(484)
I am still trying to figure this one out. The size should be 4096. The
memo text DOES seem to display properly, even though the size is screwed
up.
> char(x) --> varchar(x);
char(x), (i.e., bpchar), as well as varchar, is handled as SQL_VARCHAR.
In the future, we may have a feature that allows the user to decide how
to map Postgres data types to ODBC data types. Perhaps char(x), for
now, should be mapped to SQL_CHAR?
Byron
P.S. I have done more testing with Borland Database Explorer, and fixed
a few more things. I only had time to update the DLL not the self
extracting EXE). Download
"http://www.insightdist.com/psqlodbc/postdll.zip"; and unzip into your
\windows\system directory. You must have already installed the new
driver at least once for this to work!
Note that until the backend is patched as was discussed with Bruce in
previous conversations on the hackers/interfaces lists, Postgres varchar
type will return "I don't know" as the precision. Borland handles this
ok, but reserves a large amount of display area for the data (because it
doesnt know how big the field is).
Postgres char(x) type will show the correct length.
Byron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: dfumagalli@art-media.it, byronn@insightdist.com
Subject: Re: R: ODBC + Delphi (GREAT!) + some little thing//
In-Reply-To: <199804240931.LAA08562@mail.art-media.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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