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: 8568FC767B4AD311AC33006097BCD3D61A2915@woody.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc pgsql-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!

Regards,

Dave.

<<odbc.diff>>

Attachment Content-Type Size
odbc.diff application/octet-stream 5.9 KB

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Nick Gorham 2001-01-24 22:37:52 Re: Re: unixODBC again :-(
Previous Message Peter Eisentraut 2001-01-24 20:20:51 Re: Re: unixODBC again :-(

Browse pgsql-patches by date

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