Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine. - Mailing list pgsql-admin

From Purusothaman A
Subject Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.
Date
Msg-id 3650d0d50609110315uff51429n48e038dc6b9a482e@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.
List pgsql-admin
Thanks Martijn van Oosterhout and Marco Bizzarri.

But, according to syntax of client side lo_import and lo_export, we should have 2 variable PGconn (for esatablished connection) and lobjld (imported file ID in PostgreSQL).

I don't know how to do this in SQL statements.

pls give me sample client side sql statements.

:)
Purusothaman A

On 9/11/06, Martijn van Oosterhout <kleptog@svana.org> wrote:
On Mon, Sep 11, 2006 at 03:27:09PM +0530, Purusothaman A wrote:
> Thanks Martijn van Oosterhout,
>
> So, I have to write my own wrapper function upon the functions below.
>   1. Oid lo_import(PGconn *conn, const char *filename);
>   2. int lo_export(PGconn *conn, Oid lobjId, const char *filename);

Not sure why you need a wrapper (you didn't say which language you were
using) but those functions work exactly like the version you put in the
SQL statements, except the filenames are for the client computer with
client permissions.

Hope this helps,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFBTR4IB7bNG8LQkwRAvhPAJ9KHp9DO1EjPqbkGwBdaSaKx5J90wCfQtZ8
ijq1n/SgAlwIiEgDI6zfICg=
=Xk7N
-----END PGP SIGNATURE-----



pgsql-admin by date:

Previous
From: "Marco Bizzarri"
Date:
Subject: Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.
Next
From: "Marco Bizzarri"
Date:
Subject: Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.