Re: figuring out why I am having this issue - Mailing list pgsql-odbc

Thanks Greg.
I inherited this app and doing a one stop shop for db would be an excellent
idea, there is stuff everywhere (no error handling until I got on board, but
I have just been sticking it where the db action is.

Unfortunately I am making no progress. I tried the snapshot using the
connection DRIVER={PostgreSQL-libpq} so I am more confident at least I am
testing the correct driver version.

It is cutting my text fields off at 254 chars.
I tried making
MaxVarcharSize=32768;MaxLongVarcharSize=32768;
Thinking it might be ignoring the TextAsLongVarchar=1;
But still was cutting the text off.
So basically I can not use the libpq driver at the moment, will have to
figure out why its cutting off the text.

Joel Fradkin

Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel.  941-753-7111 ext 305

jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
 This email message is for the use of the intended recipient(s) and may
contain confidential and privileged information.  Any unauthorized review,
use, disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.




-----Original Message-----
From: Greg Campbell [mailto:greg.campbell@us.michelin.com]
Sent: Thursday, September 01, 2005 2:07 PM
To: Dave Page
Cc: Joel Fradkin; pgsql-odbc@postgresql.org
Subject: Re: [ODBC] figuring out why I am having this issue

I like the collection construct (for each)

If (error.Number <> 0) Then
    'and this for-next loop is usually in a handle_db_errors routine
instead of typing/pasting it all over my code
         'plus it become a one-stop change where I can log the error to a db
or file or event_log.
    For Each dberr in con.Errors
        Response.Write "An Error occurred................." & <br> &
vbCrLf
        Response.Write "Number: " & CStr(dberr.Number) & <br> &
vbCrLf
        Response.Write "Source: " & dberr.Source & <br> & vbCrLf
        Response.Write "NativeError: " & CStr(dberr.NativeError) &
<br> & vbCrLf
        Response.Write "Description: " & dberr.Description  & <br>
    Next
    Response.End
End If

It's all the same.


Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: Joel Fradkin [mailto:jfradkin@wazagua.com]
>>Sent: 01 September 2005 16:16
>>To: Dave Page
>>Cc: pgsql-odbc@postgresql.org
>>Subject: RE: [ODBC] figuring out why I am having this issue
>>
>>That is the error description
>>If con.Errors.Count >= 1 Then
>>        set Error = con.Errors.Item(0)
>>        'take the error code from SQL Server
>>        ErrCode = Error.NativeError
>>        response.Write(cstr(Error.Description))
>>   Response.End
>>End If
>>
>>Could be there is better method, but this what I have been using.
>
>
> Dunno if there's a better method - I would be inclined to loop round
> con.Errors.Count though - maybe something like:
>
> For X = 1 To con.Errors.Count
>     set Error = con.Errors.Item(X - 1)
>     'take the error code from SQL Server
>     ErrCode = Error.NativeError
>     response.Write(cstr(Error.Description))
> End If
> Response.End
>
>
>
>
>>I have tested putting a 300 meg text field in the data base
>>nad it worked so
>>not clear why it works on most data and this one does not.
>>I did email you the log file (not sure it is any help).
>
>
> Yeah, I can't see anything obviously wrong in it. A few things to
> consider though:
>
> - ASP seems to be retrieving data as SQL_C_CHAR, which means it's
> getting raw data, not UCS2 converted from UTF8.
>
> - ASP is retrieving data in 32KB chunks, so it would probably be worth
> making sure max_long_varchar is at least that.
>
> - Some data (quotes and such) doesn't look so good. Could it have been
> pasted from MS Word or similar?
>
> - Are you compiling the driver yourself? If so how? It seems to be using
> the old comms layer, not libpq (which I'm no longer working on). The
> giveaway is lines like the following which are for debugging the network
> protocol:
>
> connecting to the server socket...
> connection to the server socket succeeded.
> sizeof startup packet = 292
> sent the authentication block.
> sent the authentication block successfully.
> gonna do authentication
> read 15, global_socket_buffersize=8192
> auth got 'R'
> areq = 0
> auth got 'K'
> auth got 'Z'
>
> All this is now encapsulated in libpq, which doesn't log what it's
> doing.
>
> To fix this, compile on the command line:
>
> nmake /f win32.mak
>
> This should ensure you get the default libpq build. If you're doing this
> in an IDE, make sure USE_LIBPQ is defined!
>
> Regards, Dave.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster