Re: figuring out why I am having this issue

> -----Original Message-----
> From: Joel Fradkin [mailto:jfradkin(at)wazagua(dot)com]
> Sent: 01 September 2005 00:28
> To: Dave Page; pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] figuring out why I am having this issue
>
> I did try looking at it a bit and did not resolve the issue.
> I used a snapshot build (was a few days older then my build)
> and it did not
> seem to have any issue with the specific text field, but the
> asp page was
> not formatting correctly, so maybe it was doing something else.

See, told you it was late where I was :-)

It eventually gets into
ConnectionClass->ConnInfo->drivers.text_as_longvarchar. The actual value
names used in ini files, the registry or conn strings is
MaxLongVarcharSize, or B1 for short in conn strings.

> I also tried setting TextAsLongVarchar=0
> Which worked on my development box running XP pro, but did not work in
> production running win2k.
>
> I will look more tomorrow, but I could not even see what the
> variable was
> being set to, to look at the other modules.
> In my log file I could only see references to it :
> MaxLongVarcharSize=16280;

From what I can see, it's really only used for two things - 1) as the
default size for fields for which the DB doesn't report a length (see
around line 3337 in connection.c - might be a little out as I've been
playing), 2) as the size returned as the standard for certain data types
(see pgtypes.c).

I really need to see a more detailed mylog to try to figure this out -
unless you can see from it what function the E_FAIL occurs in? (it's
usually the first part of the mylog line, after the number in brackets,
and before the :

Regards, Dave