public inbox for [email protected]
help / color / mirror / Atom feedFrom: George Weaver <[email protected]>
To: pgsql-general <[email protected]>
Subject: Server side large object functions
Date: Thu, 18 Dec 2008 09:58:05 -0600
Message-ID: <FF2AB17A15534B4E896554DE5E7D2976@d800> (raw)
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
view thread (6+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Server side large object functions
In-Reply-To: <FF2AB17A15534B4E896554DE5E7D2976@d800>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox