Re: MaxLongVarChar and new lines in text

Hi Luf,

The enhanced driver does not seem to work at all with
MaxLongVarCharSize=-4 as the connect function returns false and the
mylog ends with "[2112]DETACHING PROCESS".

When using MaxLongVarCharSize=8190 I bump into another problem with my
app when trying to fetch bytea: [Microsoft][ODBC Driver Manager] Invalid
string or buffer length. It seems that this version of the driver is
handling bytea's a little bit different and not quite ready for my use.

I would prefer to use the 08.01.200 driver until the enhanced branch is
considered stable for production use.

regards,

Åsmund Kveim Lie

Ludek Finstrle wrote:
>> I'm having a problem with line breaks and the MaxLongVarChar setting.
>> I'm using Postgrsql 8.1.3 and ODBC version 08.01.0200(ansi). When I set
>> MaxLongVarChar <= 16383 it gives different results than using
>> MaxLongVarChar > 16383 or MaxLongVarChar = -4 (which is no limit). I
>
> Hello,
>
> could you try new 7.3.260 (enhanced branch) version? It's downloadable
> from www.pgfoundry.org.
>
> Hiroshi doesn't become the time for releasing 7.3.261? Or at least could
> you put patched 7.3.260 on pgfoundry? I know you put it somewhere on the
> net but I didn't remember the URL.
>
> Regards,
>
> Luf
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>