Problem with using SOCK_put_int method PGAPI_PutData - Mailing list pgsql-odbc

From Marcin Ligorowski
Subject Problem with using SOCK_put_int method PGAPI_PutData
Date
Msg-id 20080917102348.82AB016004F@f32.poczta.interia.pl
Whole thread Raw
List pgsql-odbc
Hi,
I%u2019ve detected problem with using psqlodbc driver on Sun Sparc Solaris platform.
An error occurs when Sparc converts unsigned short to unsigned int and back to unsigned short.
With default implementation 00 00 01 02 is converted to 00 00 (last two bytes are skipped), but it should be converted
to01 and 02. 
Problem occurs every time when through method SOCK_put_int two bytes integer was transferred and doesn%u2019t allow
usingPGAPI_PutData (odbc_lo_write) to put large objects to database. 

To resolve described problem I%u2019ve attached patch bellow.

Regards
Marcin

--- 769,793 ----
void
  SOCK_put_int(SocketClass *self, int value, short len)
   {
      if (!self)
         return;
      switch (len)
      {
         case 2:
+          {
+             unsigned short rv;
              rv = self->reverse ? value : htons((unsigned short) value);
              SOCK_put_n_char(self, (char *) &rv, 2);
              return;
+          }

         case 4:
+          {
+             unsigned int rv;
              rv = self->reverse ? value : htonl((unsigned int) value);
              SOCK_put_n_char(self, (char *) &rv, 4);
              return;
+          }

         default:
           SOCK_set_error(self, SOCKET_PUT_INT_WRONG_LENGTH, "Cannot write ints of that length");




----------------------------------------------------------------------
Dzwon taniej na zagraniczne komorki!
Sprawdz >>  http://link.interia.pl/f1f0e


pgsql-odbc by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: Compiler warnings in psqloodbc 08.03.0200
Next
From: Brent Austin
Date:
Subject: compiling odbc