Thread: Large Object Problem

I've setup the large object, and have tried to insert a MS Word document into
a large object field using the example at GBORG.  When I get to the 'Set rs =
cmd.Execute,' the PG computer whirrs and clanks for about 40 seconds, and
crashes with this line:  LO_IN:  error in parsing, and reports the following
line:  \320\317\021\340\241\261\032\241\000\000\000\...  The 320 sure is not
a byte!

For what it is worth, the size of the MSDOS file is 35330 bytes.  The size of
the 'object' containing the binary data is exactly have the size of the file
/ input binary data...  I don't know if that is relevant or not.

I'm running pgsql 7.3.3 on RH linux 9.0 compiled from source,  and ado 2.5 on
a win98 box.

Does anyone know what may be going on here?

John.

I had a bit of bad code in my test routine.  Once I spotted and repaired it,
things work just fine with VB5/ADO and large objects.

John.

On Friday 05 September 2003 18:25, John K. Herreshoff wrote:
> I've setup the large object, and have tried to insert a MS Word document
> into a large object field using the example at GBORG.  When I get to the
> 'Set rs = cmd.Execute,' the PG computer whirrs and clanks for about 40
> seconds, and crashes with this line:  LO_IN:  error in parsing, and reports
> the following line:  \320\317\021\340\241\261\032\241\000\000\000\...  The
> 320 sure is not a byte!
>
> For what it is worth, the size of the MSDOS file is 35330 bytes.  The size
> of the 'object' containing the binary data is exactly have the size of the
> file / input binary data...  I don't know if that is relevant or not.
>
> I'm running pgsql 7.3.3 on RH linux 9.0 compiled from source,  and ado 2.5
> on a win98 box.
>
> Does anyone know what may be going on here?
>
> John.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster