Skip site navigation (1) Skip section navigation (2)

Additional ODBC patch

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'pgsql-odbc(at)postgresql(dot)org'" <pgsql-odbc(at)postgresql(dot)org>, "'pgsql-patches(at)postgresql(dot)org'" <pgsql-patches(at)postgresql(dot)org>
Subject: Additional ODBC patch
Date: 2001-01-24 22:35:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbcpgsql-patches
Further to the previous ODBC patches I posted today, I found a couple of
problems with char array sizes having set a couple of constants to 0 for
unlimited query length and row length. This additional patch cleans those
problems up by defining a new constant (STD_STATEMENT_LEN) to 65536 and
using that in place of MAX_STATEMENT_LEN.

Another constant (MAX_MESSAGE_LEN) was defined as 2*BLCKSZ, but is now
65536. This is used to define the length of the message buffer in a number
of places and as I understand it (probably not that well!) therefore also
places a limit on the query length. Fixing this properly is beyond my
capabilities but 65536 should hopefully be large enough for most people.

Apologies for being over-enthusiastic and posting 3 patches in one day
rather than 1 better tested one!




Attachment: odbc.diff
Description: application/octet-stream (5.9 KB)


pgsql-odbc by date

Next:From: Nick GorhamDate: 2001-01-24 22:37:52
Subject: Re: Re: unixODBC again :-(
Previous:From: Peter EisentrautDate: 2001-01-24 20:20:51
Subject: Re: Re: unixODBC again :-(

pgsql-patches by date

Next:From: Bruce MomjianDate: 2001-01-24 23:01:38
Subject: Re: [PATCHES] Re: [INTERFACES] Patch for JDBC timestamp problems
Previous:From: Joseph ShraibmanDate: 2001-01-24 22:25:44
Subject: Re: [PATCHES] Re: [INTERFACES] Patch for JDBC timestamp problems

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group