public inbox for [email protected]
help / color / mirror / Atom feedServer side large object functions
6+ messages / 3 participants
[nested] [flat]
* Server side large object functions
@ 2008-12-18 15:58 George Weaver <[email protected]>
0 siblings, 2 replies; 6+ messages in thread
From: George Weaver @ 2008-12-18 15:58 UTC (permalink / raw)
To: pgsql-general <[email protected]>
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
List of functions
Schema | Name | Result data type | Argument data types | Volatility
| O
wner | Language | Source code | Description
------------+---------+------------------+---------------------+------------+---
-------+----------+-------------+-------------------
pg_catalog | lo_open | integer | oid, integer | volatile
| po
stgres | internal | lo_open | large object open
(1 row)
But if I try to find the same for lo_read I get:
development=# \df+ lo_read
List of functions
Schema | Name | Result data type | Argument data types | Volatility | Owner
| L
anguage | Source code | Description
--------+------+------------------+---------------------+------------+-------+--
--------+-------------+-------------
(0 rows)
Is there not a server side function for lo_read? If so, how do I determine
the argument types?
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.
Thanks,
George
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Server side large object functions
@ 2008-12-18 16:02 Alvaro Herrera <[email protected]>
parent: George Weaver <[email protected]>
1 sibling, 1 reply; 6+ messages in thread
From: Alvaro Herrera @ 2008-12-18 16:02 UTC (permalink / raw)
To: George Weaver <[email protected]>; +Cc: pgsql-general <[email protected]>
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
------------+--------+------------------------+------------------------------
pg_catalog | loread | bytea | integer, integer
(1 fila)
HTH,
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Server side large object functions
@ 2008-12-18 16:15 George Weaver <[email protected]>
parent: Alvaro Herrera <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: George Weaver @ 2008-12-18 16:15 UTC (permalink / raw)
To: pgsql-general <[email protected]>
From: "Alvaro Herrera" <[email protected]>
> 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
> ------------+--------+------------------------+------------------------------
> pg_catalog | loread | bytea | integer, integer
> (1 fila)
Thanks Alvaro. I didn't think to look for a variation of the function
name...
As an aside, if I do a PostgreSQL Website search for "loread", I get not
hits.
George
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [GENERAL] Server side large object functions
@ 2008-12-18 16:49 Alvaro Herrera <[email protected]>
parent: George Weaver <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Alvaro Herrera @ 2008-12-18 16:49 UTC (permalink / raw)
To: George Weaver <[email protected]>; +Cc: pgsql-general <[email protected]>; pgsql-docs
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 using libpq and C.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Server side large object functions
@ 2008-12-18 17:44 Howard Cole <[email protected]>
parent: George Weaver <[email protected]>
1 sibling, 1 reply; 6+ messages in thread
From: Howard Cole @ 2008-12-18 17:44 UTC (permalink / raw)
To: George Weaver <[email protected]>; 'PgSql General' <[email protected]>
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
www.selestial.com
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Server side large object functions
@ 2008-12-18 18:50 George Weaver <[email protected]>
parent: Howard Cole <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: George Weaver @ 2008-12-18 18:50 UTC (permalink / raw)
To: Howard Cole <[email protected]>; 'PgSql General' <[email protected]>
----- Original Message -----
From: "Howard Cole" <[email protected]>
> 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
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2008-12-18 18:50 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-12-18 15:58 Server side large object functions George Weaver <[email protected]>
2008-12-18 16:02 ` Alvaro Herrera <[email protected]>
2008-12-18 16:15 ` George Weaver <[email protected]>
2008-12-18 16:49 ` Alvaro Herrera <[email protected]>
2008-12-18 17:44 ` Howard Cole <[email protected]>
2008-12-18 18:50 ` George Weaver <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox