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

From Joel Fradkin
Subject Re: figuring out why I am having this issue
Date
Msg-id 000501c5ae63$ed6f8030$797ba8c0@jfradkin
Whole thread Raw
In response to figuring out why I am having this issue  ("Joel Fradkin" <jfradkin@wazagua.com>)
List pgsql-odbc
LOL.

Thank you much for the info.
I wish I were having a beer now myself.
I will see what I can fingure out on my own (god forbid).
I hope I did not sound like you guys don't help, I am a bit anal.
MY boss is freaking and I don't have much in the way of an answer, but it
will sort itself out in time.
As always I do appreciate all the help I have gotten thus far and do not
want to sound like I don't, because the people on this list are the best.

Joel Fradkin



-----Original Message-----
From: Dave Page [mailto:dpage@vale-housing.co.uk]
Sent: Wednesday, August 31, 2005 3:34 PM
To: jfradkin@wazagua.com; pgsql-odbc@postgresql.org
Subject: RE: [ODBC] figuring out why I am having this issue


Joel,

The problem is not that we won't help, but mainly I suspect we're in
timezones some way east of you. For example, I'm watching telly, eating a
popadom, and thinking about having a beer and going to bed!! (I'm also on my
pda, and don't have the source right now).

A hint though - look in the connectionstring in mylog, and find the actual
option name/code. Then, look in options.c (iirc), and see if you can figure
out the variable that the value gets assigned to in the ConnectionClass
object. Then, look at where that is used. The problem is /probably/ in
qresult.c, connection.c (not the #ifndef USE_LIBPQ bits), or, if you're
really unlucky, copy_and_convert_field in convert.c

Good luck, and be sure to let someone know what you're doing so they can
send dogs when you don't come back...

/D

-----Original Message-----
From: "Joel Fradkin"<jfradkin@wazagua.com>
Sent: 31/08/05 20:07:46
To: "pgsql-odbc@postgresql.org"<pgsql-odbc@postgresql.org>
Subject: [ODBC] figuring out why I am having this issue

I do not mind researching the text field problem myself, but looking at the
source code I have no idea where to look or how to approach this.

I have seen a few email where some of the developers talked about how they
were getting feed back, but to be honest never paid much attention.

I can look in the archive (and probably will), but if any of you who has
worked on the code could maybe point me in the right direction like which .c
file would be looking at

MaxLongVarcharSize I did a search and only saw it referenced in one file and
it does not look to me like it is doing anything with text fields, so I must
be missing something.



Any ideas would be a big help.



Joel Fradkin








-----Unmodified Original Message-----
I do not mind researching the text field problem myself, but looking at the
source code I have no idea where to look or how to approach this.

I have seen a few email where some of the developers talked about how they
were getting feed back, but to be honest never paid much attention.

I can look in the archive (and probably will), but if any of you who has
worked on the code could maybe point me in the right direction like which .c
file would be looking at

MaxLongVarcharSize I did a search and only saw it referenced in one file and
it does not look to me like it is doing anything with text fields, so I must
be missing something.



Any ideas would be a big help.



Joel Fradkin






pgsql-odbc by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: Unicode support
Next
From: "Dave Page"
Date:
Subject: Re: figuring out why I am having this issue