Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

Thank you Marco Bizzarri.My solution would be C API.Thanks for you prompt response.:)Purusothaman AOn 9/11/06, Marco Bizzarri <[EMAIL PROTECTED]> wrote: On 9/11/06, Purusothaman A <[EMAIL PROTECTED]> wrote:> Hi Marco Bizzarri and Martijn van Oosterhout,>>> Thanks for your valuable reply. >> I am t

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

On 9/11/06, Purusothaman A <[EMAIL PROTECTED]> wrote: Hi Marco Bizzarri and Martijn van Oosterhout, Thanks for your valuable reply. I am trying to execute all query from VC++ through CDatabase::ExecuteSQL(sQueryString) function call. ie, via programming, not by manual entering query statement

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

Hi Marco Bizzarri and Martijn van Oosterhout,Thanks for your valuable reply.I am trying to execute all query from VC++ through CDatabase::ExecuteSQL(sQueryString) function call.ie, via programming, not by manual entering query statements. so, in my situation I can construct a string and pass on to

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

On Mon, Sep 11, 2006 at 12:56:11PM +0200, Marco Bizzarri wrote: > I will try to explain it with a sample session: this is for creating > and writing a blob. Oh, I was looking for lo_read/lo_write, which don't exist. It's loread/lowrite. Inconsonistant naming is irritating. It doesn't help the OPs

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

I will try to explain it with a sample session: this is for creating and writing a blob. From the psql prompt (> are the commands, the other are the results). begin ; BEGIN; SELECT lo_creat(131072) ; lo_creat -- 198705 (1 row) (this is the OID number of the newly created large o

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

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

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

Actually, you can use direclty the lo_create, lo_open, lo_read and lo_write directly into your SQL code, instead of having to write a wrapper function. It is not simple, but it can be done. I don't have a general example: we have done this in a couple of our projects, one being public availabe (w

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

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);

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

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); Am I right?:)Purusothaman AOn 9/11/06, Martijn van Oosterhout

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

Short answer, you can't. The database server can obviously only access things on the database server. Since SQL is also executed on the server, no SQL statements can access stuff on the client computer. If you want to load a file on the client side to the server, you need to open the file and copy

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

Hi Martijn van Oosterhout,Thanks for your valuable reply.Yes I misunderstood the documentation.Then, I searched PostgreSQL documentation for equivalent client-side functions.But I found only C programming APIs instead of SQL functions. I want functions which is usable in SQL statements.Can you give

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

On Sat, Sep 09, 2006 at 05:19:26PM +0530, Purusothaman A wrote: > I usually log in to postgresql server with admin username. > > But whatever its, according to documentation, if client machine's user has > write access > permission, this query should successfully be executed. Read carefully, you

Re: [GENERAL] [ADMIN] Problem with lo_export() and lo_import() from remote machine.

Hi Milen A. Radev,Thank you for your response.I have read this in PostgreSQL documentation. I usually log in to postgresql server with admin username.But whatever its, according to documentation, if client machine's user has write access permission, this query should successfully be executed.Both