Thread: OIDs > 2147483647 still a problem for the Unicode version ( 32 bit ) ?

OIDs > 2147483647 still a problem for the Unicode version ( 32 bit ) ?

From
"Jan-Peter Seifert"
Date:
<div style="font-family: Verdana;font-size: 12.0px;"><div>Hello,</div><div> </div><div class="signature">the very same
serverinstance / database that caused problems because of high OIDs for the ANSI version of psqlODBC is still (?)
causingproblems for the Unicode version ( tested with v9.02.01.00 ):</div><div class="signature"><a
href="http://www.postgresql.org/message-id/20110103141602.204670@gmx.net"
target="_blank">http://www.postgresql.org/message-id/20110103141602.204670@gmx.net</a></div><div
class="signature"> </div><divclass="signature">OIDs get clamped at 2147483647 -no problem with the ANSI
version.</div><divclass="signature"> </div><div class="signature">Could you check this, please?</div><div
class="signature"> </div><divclass="signature">Thank you very much!</div><div class="signature"> </div><div
class="signature">Peter</div></div>

Re: OIDs > 2147483647 still a problem for the Unicode version ( 32 bit ) ?

From
Hiroshi Inoue
Date:
(2013/08/01 0:32), Jan-Peter Seifert wrote:
> Hello,
> the very same server instance / database that caused problems because of
> high OIDs for the ANSI version of psqlODBC is still (?) causing problems
> for the Unicode version ( tested with v9.02.01.00 ):
> http://www.postgresql.org/message-id/20110103141602.204670@gmx.net

I don't understand how the above thread is related to psqlodbc.

> OIDs get clamped at 2147483647 -no problem with the ANSI version.
> Could you check this, please?

Could you send me the Mylog output of a bad result case?

regards,
Hiroshi Inoue



Re: OIDs > 2147483647 still a problem for the Unicode version ( 32 bit ) ?

From
"Jan-Peter Seifert"
Date:
Hello,

> Gesendet: Donnerstag, 01. August 2013 um 12:55 Uhr
> Von: "Hiroshi Inoue"

psqlODBC v9.02.0100 has been successfully tested with a different instance that has high system OIDs as well (
v8.04.0200that doesn't have the bug fix was uninstalled first ). 
v9.01.0100 worked for the 'first' instance a day later.
Maybe the old version has been cached by Windows somehow?
So there's no regression. Sorry for the confusion.

Best regards,

Peter