DevHeads.net

ODBC

ODBC binary downloads -- SHA256sums?

Trying to figure out how to validate my downloads.

postgresql install odbc driver

hello!

Centos 7.0
install 9.2 driver psqlodbc-09.02.0100.tar.gz
./configure

checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... yes
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for library containing SQLGetPrivateProfileString...

install ODBC driver

hello!

install 9.5 driver
./configure

install 9.2 driver
./configure

祝好!

互联网ITS集团,流通线.行业BU 魏磊
电话:029-89633928
地址:陕西省 西安市 雁塔区 天谷八路 中软基地

ODBC connectin string for Postgres db needed

Hi,

Is this a good contact to obtain the connection string to a Postgres database? We would like to connect to Postgres from Cognos 10.2 /Framework Manager.

Thanks so much in advance for any assistance that you can bring us.

Challenge Accepted!

Gonzalo Ordonez
HRIS Administrator
SOS International LLC
1881 Campus Commons Drive, Suite 500
Reston, VA 20191
o. 703.391.9680, ext. 1051 | d. 703.774.1836 | f.

Severe bug in SQLPrimaryKeys function in psqlODBC 09.06.0500

Hello,

there seems to be a new bug in the SQLPrimaryKeys function - e.g.

Error Notification

Dear Support,

Most recent version of PostgreSQL ODBC Driver that we are using it for GreenPlum v 4.3.9.1 is throwing error when character varying <255 within the linked SQL Server.

ODBC for Linux/RHEL - no 9.6.5 binary build yet?

Hi,

I’ve been checking <a href="https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-6-x86_64/" title="https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-6-x86_64/">https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-6-x86_64/</a>

and while many components were updated to 9.6.5, the latest ODBC is still 9.6.4.1:

postgresql96-odbc-09.06.0410-1PGDG.rhel6.x86_64.rpm.

Any plans for updating it?

Thank you.

Georgiy Pruss

psqlODBC 09.06.0500 Released

Hi, all.

We are pleased to annouce the release of psqlODBC 09.06.0500.
This is a some bugfix release.
please see the notes at:
<a href="https://odbc.postgresql.org/docs/release.html" title="https://odbc.postgresql.org/docs/release.html">https://odbc.postgresql.org/docs/release.html</a>

psqlODBC may be downloaded from in source, Windows Installer,
merge module, and basic zip file formats.

New Windows installer installs both 32-bit and 64-bit driver at once
on 64-bit OS.

SQL literal with SJIS hankaku-kana character cause missing escape

Hello, psqlODBC team.

We got a bug.
Its reproduce program and log are attached.

An SQL string that contains string leteral ended odd number of
SJIS hankaku-kana character could cause misssing the next escape.

We haven't fixed it yet.

best regards,
Haruka Takatsuka / SRA OSS, Inc. <a href="http://www.sraoss.co.jp" title="http://www.sraoss.co.jp">http://www.sraoss.co.jp</a>

Compilation failure with nmake since 503bb09

Hi all,

With the latest code of Postgres ODBC, I am seeing compilation
failures of this kind:
c:\Users\ioltas\git\pgodbc\connection.h(27) : fatal error C1083:
Cannot open include file: 'pqexpbuffer.h': No such file or directory

It seems to me that 503bb09 forgot to update win64.mak to include
$(PG_INC)/internal in the paths to scan for headers. Please see
attached a patch.

Regards,

Bug in PostgreSQL ODBC - in names with dollar

Hi,

I’m sorry, I really tried to register at pgsql-odbc list at postgresql.org, using different email addresses, but it didn’t’ work.

I saw that you may deal with this problem.

When UseServerSidePrepare is set to 1 (which is default, I guess), any names with $ in them cause error:

“The # of binded parameters < the # of parameter markers”

It’s both on Windows and Linux.

It seems that PG tries to use un-paired ‘$’ symbols as parameter marks for the server-side prepare/execute feature, even if there’s no PREPARE or EXECUTE statements.

I believe, PG should not par

ODBC crash after DB cleanup

Hi,

We are using PostgreSQL release 9.3.14 and psqlODBC release 09.03.0400 configured over linux based OS. We are encountering an issue in production where we are observing ODBC crash after rehoming(cleanup of database) and BTS sites are going down after this activity.

Q: Is there a way to force psqlODBC with enabled UseDeclareFetch to commit statements and avoid nesting transactions (savepoints)?

Since generated cursors are declared WITH HOLD they would survive COMMIT, and I assume, release resources on the server. I know that this would not be appropriate for all statements!

I am trying to determine if there is a combination of statement attributes or some other settings that would make the ODBC driver operate in such fashion. I was hoping there is some combination of (statement) settings that would tell the driver that we are sending a forward only, read only, statement.

A POSSIBLE BUG: The ODBC standard procedure call ("{ CALL function(param) }") is disallowed in ReadOnly ODBC mode whereas "SELECT * FROM function(param)" is let through.

* A POSSIBLE BUG: The ODBC standard procedure call ("{ CALL function(param) }") is disallowed in ReadOnly ODBC mode whereas "SELECT * FROM function(param)" is let through.

Good morning.

Since the ODBC "{CALL..}" statement is translated to a "SELECT..FROM..." this seems like an error.

-- Regards, Matej.

Segmentation fault of psqlodbcw.so during connect to postgres server

hi

Because i send the email to your organization failed with company server, so i change the server and send the bug description again.

psql odbc expert, recently we met an occasional issue that psqlodbcw.so will be crashed during connect the postgres server.

psqlodbcw.so version: psqlodbc-09.05.0400

postgres server version: postgresql-9.6.2

Test step:

1 Start up postgres server

2 Launcher a process which call psqlodbc driver to connect and disconnect postgres server insequential.

3 Fast shutdown the postgres server, however, the client process will crash occasionally.

Crash

The psqlodbcw.so will be crashed during connect to postgres server

hi

psql odbc expert, recently we met an occasional issue that psqlodbcw.so will be crashed during connect the postgres server.
psqlodbcw.so version: psqlodbc-09.05.0400
postgres server version: postgresql-9.6.2

Test step:
1 Start up postgres server
2 Launcher a process which call psqlodbc driver to connect and disconnect postgres server in sequential.
3 Fast shutdown the postgres server, however, the client process will crash occasionally.

Crash information:

Program terminated with signal SIGSEGV, Segmentation fault.
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
106 in ../sysdeps/x8

Connectivity error: Could not convert from the current locale to wide characters

After installing latest odbc driver my application throws error

Connectivity error: Could not convert from the current locale to wide
characters

Application runs in Windows 10 in windows-1257 locale
Using unicode driver
Postgres 9.6
database encoding is unicode

How to fix this?
How to force earlier driver behaviour which worked OK ?

Andrus.

There is a bug in psqlodbcw.so during connect to postgres server

hi

psql odbc expert, recently we met an occasional issue that psqlodbcw.so will be crashed during connect the postgres server.
psqlodbcw.so version: psqlodbc-09.05.0400
postgres server version: postgresql-9.6.2

Test step:
1 Start up postgres server
2 Launcher a process which call psqlodbc driver to connect and disconnect postgres server in sequential.
3 Fast shutdown the postgres server, however, the client process will crash occasionally.

Crash information:

Program terminated with signal SIGSEGV, Segmentation fault.
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
106 in ../sysdeps/x8

Connection failure with invalid connection option "gsslib" for 09.06.0410

Hi all,

When updating the ODBC driver from 09.06.0310 to 09.06.0410 (Yes I
lagged behind one release!), I have noticed a failure when connecting
to a Postgres instance on Windows:
cmd=c:/python27/python check_odbc.py --dsn uninst_std_noimpact_srm
--user test_odbc --pwd passw0rd --port 5444
stdout=Connecting odbc :
DSN=uninst_std_noimpact_srm;Uid=test_odbc;Pwd={passw0rd};

stderr=Traceback (most recent call last):
File "check_odbc.py", line 111, in main
check_odbc_connection(conn_str)
File "check_odbc.py", line 15, in check_odbc_connection
cnxn = pyodbc.connect(conn_str)
Error: ('0

Postgre driver(9.06.04.00) connected to Amazon redshift, is returning wrong count in SQLRowCount

Hi,

I am Asif from IBM and need an urgent help on following.

We are facing an issue with postgre driver(9.06.04.00) connecting to
Amazon Redshift database.
We are executing the following query
SELECT DISTINCT customer_id INTO <New_Table_NAME> FROM
<Existing_Table_Name>.

The query gets executed properly and the table also gets created.
The problem here is that postgre driver returns wrong count(affected
number of rows) for this query as output paramter in SQLRowCount.
The sequence of driver calls are as follows
SQLDriverConnect - to connect to driver
SQLGetInfo (hDBC, SQL_ODBC_API_CONFORM

A possible bug candidate in the 9.6.0411 when using the ServerSidePrepare option

* A possible bug candidate in the 9.6.0411 when using the ServerSidePrepare option

Hi.

The statement bellow will trigger a false error. This error disappears if I disable the ServerSidePrepare option in the driver, or if I quote the table column names. I guess something is triggered by the presence of the dollar sign within the column name.

I was doing the tests using the 32-bit Unicode 9.6.0411 build.

[11.969]STATEMENT ERROR: func=build_libpq_bind_params, desc='', errnum=32, errmsg='Parameters exist but IPD isn't set.

New bug or regression between 9.6 releases 0410 and 0310

* New bug or regression between 9.6 releases 0410 and 0310

Win64/Win32 ODBC: With the 0410 release we are seeing a ODBC manager error "[Microsoft][ODBC Driver Manager] Invalid string or buffer length" on a particular row when fetching a BYTEA field. This was a single field SELECT. We can read the value from all preceding rows so it to do something with this field value.

The error disappears when we revert back to the 0310 ODBC release.

I can send you the exact value of the BLOB in a private email if necessary.

When doing installcheck, an error message "unresolved external symbol _get_test_dsn ..." displays.

Hi, all

Operating System:
Windows7 64bit, psqlODBC 09.06.0410
PostgreSQL 9.6.1 on CentOS7

The following trouble occurred when doing installcheck.

I think $(COMOBJ) is needed for compiling reset-db.c.
What do you think?

psqlodbc-09.06.0410/test/win.mak

SQL_QUERY_TIMEOUT

When SQL_QUERY_TIMEOUT was added it was defined as SQLULEN as per the current ms odbc spec. But as of 3.5 wasn't it a SQLUINTEGER?

It looks like the majority of the other attributes like (SQL_NOSCAN, SQL_RETRIEVE_DATA, etc) are defined as SQLUINTEGER.

This could cause a memory overwrite if its treated like an SQLUINTEGER like the other attributes.

Thanks,
Keith

ODBC application works while libpq fails

Hi,
I have a very weird situation.

I am trying to develop an application which will connect to the PostgreSQL
server thru 2 different methods: thru the ODBC and using libpq.

Environment:
MacOSX 10.8.
Xcode 4 (latest available for 10.8)
PostgreSQL 9.1 - original from OSX.
Application is compiled with the UNICODE
iODBC DM for OSX 10.8.
Both application and DB server running on the same machine.
The database I'm using was created with the default parameters (just
CREATE DATABASE draft).

When I connect with the ODBC driver, the application works as expected
- no errors or problems.

However whe

HY0000 on SQLDescribeParam

Hi, ALL,
I'm getting an error calling SQLDescribeParam() on PostgreSQL 9.4.

The message obtained by SQLGetDiagRec() reads:

[quote]
Unfortunately couldn't get this parameter info.
[/quote]

I'm on OSX 10.8 using iODBC DM.
The PostgreSQL ODBC driver is not the current one (at least I don't think so).

This same call succeeded with MS SQL Server.

Does anybody have an idea of how to work around this?

psqlODBC 09.06.0410 Released

Hi, all.

We are pleased to annouce the release of psqlODBC 09.06.0410.
This is a some bugfix release.
please see the notes at:
<a href="https://odbc.postgresql.org/docs/release.html" title="https://odbc.postgresql.org/docs/release.html">https://odbc.postgresql.org/docs/release.html</a>

psqlODBC may be downloaded from in source, Windows Installer,
merge module, and basic zip file formats.

New Windows installer installs both 32-bit and 64-bit driver at once
on 64-bit OS.

Static buffer is not thread safe

Hi psqlODBC Team,

A few days ago, I sent an email with the subject '"relation does not exist" errors with psqlODBC' which described an intermittent error I observed and included a demo project to recreate the problem. The error was 'column "column_name" of relation "table_name" does not exist'.

I haven't heard anything back so I don't know what the status is, but I have found the source of the problem. In the misc.c source file, the function quote_table() declares a static buffer that is not thread safe:

static char buf[200];

Thanks,

Scott

postgresql odbc

Dears

i have oracle on red hat 5.3 i want to connect to postgresql 9.3 by DB LINK from oracle to postgresql 9.3,
So what the best postgresql-odbc i have to install in red hat 5.6.

Is postgresql-odbc 9.3 (same database version) or postgresql-odbc 9.5.

and do you have any documentation for the connection and how using it

Regards
Malik Alrawahi

"relation does not exist" errors with psqlODBC

Hi Folks,

Under certain circumstances, the following error is encountered:

ERROR: column "column_name" of relation "table_name" does not exist

Here are the facts:

- The problem seems to only occurs when under load. 
- The database version is 9.6.3
- The problem exists in ODBC versions 09.03.0300, 09.06.0310 and 09.06.0400, but not in 09.00.0310 (versions not mentioned have not been tested)
- The column name in the error exists, but it belongs to another table than the one reported in the error.
- To the best of my knowledge, only inserts and updates are affected.

I put together an

psqlODBC 09.06.0400 Released

Hi, all.

We are pleased to annouce the release of psqlODBC 09.06.0400.
This is a some bugfix release.
please see the notes at:
<a href="https://odbc.postgresql.org/docs/release.html" title="https://odbc.postgresql.org/docs/release.html">https://odbc.postgresql.org/docs/release.html</a>

psqlODBC may be downloaded from in source, Windows Installer,
merge module, and basic zip file formats.

New Windows installer installs both 32-bit and 64-bit driver at once
on 64-bit OS.

ODBC Drivers won't install properly

I have never had a problem installing the ODBC drivers on any version of windows thru V8.1-64, until now. I'm trying to install them on win7-64 and win10-64, and the install wizards say they completed, but they do not show up in the ODBC Data Source Administrator. They show in the Programs and Features list of installed programs.

Config documentation about PROTOCOL=

The documentation of the PROTOCOL=<value> option in config.html seems out
of sync with the current driver behavior (since 09.05.0100).

As I interpret the code and according to my tests, the driver ignores
anything in <value> before a dash and if there is a dash, then the
following number, parsed via atoi(), is used as the rollback_on_error
setting. Even when using SSL.

This discrepancy has recently caused confusion in a customer project, so I
would like to fix the documentation.

Is the config.html file generated? If so where is the actual source?

Thanks, Jan

Build the PostgreSQL ODBC Driver on Windows

hi developer:
I build the PostgreSQL ODBC Driver on Windows10 X64,but have some trouble.
I download psqlodbc-09.05.0400 to build it with Microsoft Visual Studio 2010.
I use following two methods to build.
1.Use NMAKE.exe to build the driver.
The following error:
Building the PostgreSQL ANSI 3.0 Driver for ...

Using PostgreSQL Include directory: C:\Program Files (x86)\PostgreSQL\9.5\include
Using PostgreSQL Library directory: C:\Program Files (x86)\PostgreSQL\9.5\lib
cd installer && "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\nmake.exe" -f installer.mak CFG=Release

more bugs with returning 0 for malloc(0)

Hello, psqlODBC team.

I'm reporting a bug.
This simular to the following bug.

<a href="https://git.postgresql.org/gitweb/?p=psqlodbc.git;a=commit;h=ae12eef5ccb754d1cd9a4f12e8e88e56e0497bc2" title="https://git.postgresql.org/gitweb/?p=psqlodbc.git;a=commit;h=ae12eef5ccb754d1cd9a4f12e8e88e56e0497bc2">https://git.postgresql.org/gitweb/?p=psqlodbc.git;a=commit;h=ae12eef5ccb...</a>

Some codes consider it error when zero size malloc/calloc return NULL.
I think we should add zero size check codes there.

columninfo.c: CI_read_fields_from_pgres(), CI_set_num_fkields()
convert.c: QB_initialize_copy()
bind.c: create_empty_bindings()
bind.c: create_empty_gdata()

Unexpected SQL execution failures reported on AIX with the latest psqlodbc.

mylog:
[1]about to begin SC_execute
[1]libpq_bind_and

Fail to install psqlodbc due to libpq version incorrect

Hi,

I failed to install psqlodbc on AIX 7.1 (64-bit) since it requires libpq > 9.2 version.
I checked there is libpq in my AIX but I have no idea what the version is and how to upgrade it.

Indeed I need the odbc driver to connect from Oracle -> Oracle Gateway -> unixODBC -> PostgreSQL.
However the driver in unixODBC is too old and so I would like to try psqlodbc.

Hope you can help.

Many thanks,
Joe

This message and any attachment are confidential and it may be a criminal offence for you to disclose or use them without authority.

Version “psqlodbc_09_06_0300-x64” & “psqlodbc_09_06_0310-x64” not working on Windows system

Hi,

First of all thank you for making this available for the public

Possible sslmode values

Hi,

I'm trying to figure out what the possible values for the sslmode option for psqlODBC are. Are the options for libpq (<a href="https://www.postgresql.org/docs/9.3/static/libpq-ssl.html" title="https://www.postgresql.org/docs/9.3/static/libpq-ssl.html">https://www.postgresql.org/docs/9.3/static/libpq-ssl.html</a>) the same options that may be used with psqlODBC?

Best regards

UseServerSidePrepare not working on aix

I'm getting an error like the connection was dropped trying to read data.

ERROR: CLI open cursor error: Could not receive the response, communication
down ??

9.6.031 driver using 9.4.12 libpq.

I have to turn off UseServerSidePrepare to get a successful read.

Anyone run into anything like this? I wondering/hoping if it is something simple like a configure option or something at build time.

Thanks,
Keith

GSS from windows

Hi there,
I attempted to enable GSS to get authentication against my Linux server by
selecting 'use gssapi for GSS request' in the DSN configuration dialog and
then ran a query using the DSN. It gives an error - 'invalid connection
option "gsslib"'. Looking into it a bit further it looks like Libpq is
compiled without GSS. What would you suggest?
Thanks and regards
Matt

Update

Hello,

We are using psqlodbc to update a Postgresql database from embedded sql
for cobol.
We have a strange behaviour : the first time we update, the update is
correct (sqlcode 0).

odbc

Which of the pgodbc drivers should I use with delphi 5?

thanks

Need help to choose which ODBC driver to use

Hi,

I am quite new to PostgreSQL and I need some help to choose the ODBC driver
to install on a new 64bit SQL server 2014 standard. It is on a Windows
Server 2012 R2 OS that is recently set up.

I need to set up a ODBC Data Sources and link server on the SQL server to
query data on a 64bit PostgreSQL 9.4.5 server. The PostgreSQL is on a 64bit
Windows Server 2008 R2 Enterprise OS.

I go to this link
<a href="https://www.postgresql.org/ftp/odbc/versions/msi/" title="https://www.postgresql.org/ftp/odbc/versions/msi/">https://www.postgresql.org/ftp/odbc/versions/msi/</a>

and download psqlodbc_09_06_0310-x64.zip

and install it on the SQL server.

psqlODBC 09.06.0310 Released

Hi, all.

We are pleased to annouce the release of psqlODBC 09.06.0310.
this is a bugfix release which crashes in MSAccess used by Windows.
please see the notes at:
<a href="https://odbc.postgresql.org/docs/release.html" title="https://odbc.postgresql.org/docs/release.html">https://odbc.postgresql.org/docs/release.html</a>

psqlODBC may be downloaded from in source, Windows Installer,
merge module, and basic zip file formats.

New Windows installer installs both 32-bit and 64-bit driver at once
on 64-bit OS.

Issue with psqlodbc and MSACCESS

Hello

I have done a test upgrade of psqlodbc to 9.6.300 running on Windows 10 and I now find my Microsoft access database which is using it crashes as soon as it tries to use the odbc connection.

The PostgreSQL database version is 9.4.11

I have enable the mylog driver option but do not get a mylog_????.log file created

I have pasted an error that is the event log related to the issue

Faulting application name: MSACCESS.EXE, version: 16.0.7668.2074, time stamp: 0x588def7a
Faulting module name: psqlodbc35w.dll, version: 9.6.3.0, time stamp: 0x590f2975
Exception code: 0xc0000005
Fault offset

psqlODBC 09.06.0300 Released

Hi, all.

We are release of psqlODBC 09.06.0300. this is a some bugfix release.
please see the notes at:
<a href="https://odbc.postgresql.org/docs/release.html" title="https://odbc.postgresql.org/docs/release.html">https://odbc.postgresql.org/docs/release.html</a>

psqlODBC may be downloaded from in source, Windows Installer,
merge module, and basic zip file formats.

New Windows installer installs both 32-bit and 64-bit driver at once
on 64-bit OS.

SQL_QUERY_TIMEOUT

Hi,

I found that in psqlODBC 09.05.0300 Release was implemented
SQL_QUERY_TIMEOUT.
How it works?
I need to set up odbc connection in Debian, that send me error(disconnet
dead connection) after defined time, but I can`t find how can I setup
SQL_QUERY_TIMEOUT in odbc.ini.
I have installed latest odbc driver(09.06.0200)

Regards

PostgreSQL, and ODBC statement handles

I am running a benchmark (TPCx-V) with a single process on the client system handing all the load. Each connection to the server is in a separate thread with its own connection to PGSQL, and its own connection handle and statement handle. I am facing a contention problem with ODBC on the client side. strace and perf top show we are serializing over what appears to be accesses to the ODBC statement handlepgsq.

Handling the case where character conversion fails

Hello,

I think the attached patch is necessary to handle the case where msgtowstr() fails to convert the character data. Could you check this?

Regards
Takayuki Tsunakawa

Re: [ODBC] Problem with postgres 9.6 ODBC drivers

Team,

Can you please help us on this, as we were not able to continue our further testing with 09.06 Windows ODBC drivers.

Thanks,
Jegan

Hi Postgres ODBC team,

Our application is failing with the latest windows odbc (postgres) drivers, because it's not updating sequence table at al.
So we will always get the same id when we try to create any new object, ending up in unique constraint violation error.
Debugged postgres odbc driver code (<a href="https://ww" title="https://ww">https://ww</a>

Server Closed the connection unexpectedly

Hello,
I downloaded odbc driver for mongodb from site("psqlodbc_09_06_0200-x64"), i try to connect to my mongodb server via this odbc server(on Windows) but the error which is attached screen shot this email
was occured. while this trying, i can see openned connection on my mongodb server.
I try to find solution on web forums, but I didn't find.

Could you help me for this situation?

Best Regards

Mehmet Keles

PGAPI_ProcedureColumns and no support for table output arguments

Hi Everyone,

While debugging the driver, I've noticed that there is no support for table output arguments (proargmodes = 't').

Is this intentional or is it a simple omission or even a bug?

Regards,
Matej Mihelič.

Problem with postgres 9.6 ODBC drivers

Hi Postgres ODBC team,

Our application is failing with the latest windows odbc (postgres) drivers, because it's not updating sequence table at al.
So we will always get the same id when we try to create any new object, ending up in unique constraint violation error.
Debugged postgres odbc driver code (<a href="https://www.postgresql.org/ftp/odbc/versions/src/" title="https://www.postgresql.org/ftp/odbc/versions/src/">https://www.postgresql.org/ftp/odbc/versions/src/</a>) and found the below:

File: results.c
Method: static void KeySetSet(const TupleField *tuple, int num_fields, int num_key_fields, KeySet *keyset)
Problematic change: keyset->status = 0;

We will execute all queries with status 1024, now for some

COLUMN_SIZE for bytea now equals -4 (09.05 vs 09.06)

Hi,

I noticed Ubuntu 12.04 package odbc-postgresql updated
from 09.05.0400 to 09.06.0200.

Since then, a 'bytea` column info obtained with SQLColumns
no longer reports COLUMN_SIZE larger than 0, but equal to -4.
AFAIU, -4 means SQL_NO_TOTAL.

Which change in the release notes corresponds to that?
<a href="https://odbc.postgresql.org/docs/release.html" title="https://odbc.postgresql.org/docs/release.html">https://odbc.postgresql.org/docs/release.html</a>

Is it this one?

18. Change the default of ByteaAsLongVarBinary from 0 to 1

Best regards,

psqlODBC 09.06.0200 Released

Hi, all.

We are release of psqlODBC 09.06.0200. this is a some bugfix release.
please see the notes at:
<a href="https://odbc.postgresql.org/docs/release.html" title="https://odbc.postgresql.org/docs/release.html">https://odbc.postgresql.org/docs/release.html</a>

psqlODBC may be downloaded from in source, Windows Installer,
merge module, and basic zip file formats.

New Windows installer installs both 32-bit and 64-bit driver at once
on 64-bit OS.

ODBC connections go dead after a failed query?

Hi,

We have some legacy SQL queries that works on SQL Server but not on
PostgreSQL due to SQL Server-specific syntax, which we are working to
migrate. The problem is sometimes psqlodbc just cannot seem to reset itself
after a bad query and simply go dead.

Issues with OUT parameters in stored procedures

Hi,

we have here an issue that stored procedures cannot be found. This issue comes up with the newest psqlodbc version.

SQLGetTypeInfo tiny column sizes

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.

Matrix driver ODBC / Postgresql database version

HI,

Do you have a matrix for ODBC driver version (windows) vs PostgreSQL database version (redhat) ?

Regards
Francis Cherat

Syndicate content