From: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
---|---|
To: | Michael Kleehammer <michael(at)kleehammer(dot)com> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: SQLGetTypeInfo tiny column sizes |
Date: | 2017-02-21 08:29:46 |
Message-ID: | 86bc5590-e0a9-446e-6380-330b44b8d375@dream.email.ne.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hi Michael,
On 2017/02/18 7:50, Michael Kleehammer wrote:
> I’m the maintainer of pyodbc which is a Python / ODBC bridge and am
> getting really poor performance from psqlODBC varchar and wvarchar
> writes. The project has to work with all drivers so I have to use
> whatever the driver says - in this case SQLGetTypeInfo for these types
> return a column size of 255 bytes. Any writes above this size have be
> sent 255 bytes at a time using SQLPut, but this is obviously
> significantly slower.
You can set the max varchar size using MaxVarcharSize option in a
connection string or Datasource setting.
regards,
Hiroshi Inoue
>
> Now, I’ve provided a way to override it, but I can’t do it
> automatically for people so it would be ideal if we could review what
> the proper value should be.
>
> https://github.com/mkleehammer/pyodbc/wiki/Connecting-to-PostgreSQL
>
> Do you see any problem increasing this size in the driver?
>
> Thanks,
> Michael Kleehammer
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Apsel | 2017-02-21 08:39:24 | Re: Issues with OUT parameters in stored procedures |
Previous Message | Inoue, Hiroshi | 2017-02-21 04:55:39 | Re: Issues with OUT parameters in stored procedures |