| From: | Hannu Krosing <hannu(at)skype(dot)net> |
|---|---|
| To: | Larry McGhaw <lmcghaw(at)connx(dot)com> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Dann Corbit <DCorbit(at)connx(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Selecting a constant question |
| Date: | 2007-06-13 04:29:30 |
| Message-ID: | 1181708970.6786.1.camel@hannu-laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ühel kenal päeval, T, 2007-06-12 kell 13:40, kirjutas Larry McGhaw:
> For what its worth .. Your statement about why we are the first people
> to mention this problem really got me thinking. Anyone who would
> attempt to write an ODBC driver for Postgres would run into the exact
> same issue. So I installed the official Postgres ODBC driver, and ran
> the identical query and here are my results:
>
> I probably should have looked at this first .... There is a whole
> Postgres ODBC dialog dedicated to the very subject of this thread:
> Handling of "unknown" data sizes. The pgodbc driver is configured to
> treat unknowns as varchar(255) by default,
> As shown by my example below. This can be configured up or down as
> desired.
BTW, what is the reason you are writing your own ODBC driver ?
What problems in the official one are you trying to solve ?
--------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chuck McDevitt | 2007-06-13 04:30:27 | Re: Selecting a constant question: A summary |
| Previous Message | Tom Lane | 2007-06-13 01:06:15 | Re: Selecting a constant question: A summary |