- Original Message -
From: "Howard Cole"
If you use Npgsql (.NET library) rather than ODBC - there are functions
for reading large objects into memory.
Cool!
I've been meaning to have a look at Npgsql - maybe this is the nudge I need!
Thanks,
George
--
Sent via pgsql-general
George Weaver wrote:
My objective it to read a large object into memory as opposed to
exporting it to a disk file.
I'm using version 8.3.3, psqlODBC 8.2.2 and vb.net.
If you use Npgsql (.NET library) rather than ODBC - there are functions
for reading large objects into memory.
Howard Cole
George Weaver wrote:
> As an aside, if I do a PostgreSQL Website search for "loread", I get not
> hits.
Apparently these functions are not documented at all :-( Most of the
chapter on large objects
http://www.postgresql.org/docs/8.3/static/lo-funcs.html
seems predicated on that one will be usi
From: "Alvaro Herrera"
George Weaver wrote:
But if I try to find the same for lo_read I get:
development=# \df+ lo_read
alvherre=# \df loread
Listado de funciones
Schema | Nombre | Tipo de dato de salida | Tipos de datos de
argumentos
+
George Weaver wrote:
> But if I try to find the same for lo_read I get:
>
> development=# \df+ lo_read
alvherre=# \df loread
Listado de funciones
Schema | Nombre | Tipo de dato de salida | Tipos de datos de argumentos
++
Hi,
The PostgreSQL manual indicates that:
"There are server-side functions callable from SQL that correspond to each
of the client-side functions described above."
In psql I can get the argument data types for lo_open:
development=# \df+ lo_open
