pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Purusothaman A <purusothaman.a@gmail.com>
To: Martijn van Oosterhout <kleptog@svana.org>
To: Marco Bizzarri <marco.bizzarri@gmail.com>
To: Milen A. Radev <milen@radev.net>
To: pgsql-admin@postgresql.org
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.
Date: Mon, 11 Sep 2006 19:00:00 +0530
Message-ID: <3650d0d50609110630p7c0fa6dfsb9dbc995f4406680@mail.gmail.com> (raw)
In-Reply-To: <3f0d61c40609110356n53e6da12h26d54cb74f448263@mail.gmail.com>
References: <3650d0d50609090407j237bb710h9bde1675c773925d@mail.gmail.com>
	<edu8r6$k56$1@sea.gmane.org>
	<3650d0d50609090449q2aec1098xc3b62dd169de5843@mail.gmail.com>
	<20060909120613.GA10336@svana.org>
	<3650d0d50609110215j7361bc2dj55e6d7d73af1d07d@mail.gmail.com>
	<20060911093819.GA15769@svana.org>
	<3650d0d50609110257m7b216b27nabb8ae87f7852e2@mail.gmail.com>
	<20060911100336.GB16564@svana.org>
	<3650d0d50609110315uff51429n48e038dc6b9a482e@mail.gmail.com>
	<3f0d61c40609110356n53e6da12h26d54cb74f448263@mail.gmail.com>

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 this function to
execute the query string.

Whatever the string I pass to ExecuteSQL() function, gets executed and I
cannot get any result retured from the passed query string [like OID -
198705, from lo_create()].

Now, can you suggest me how to achieve it?

And one more clarification, what is the value 131072? How can I get this
vlaue?

According to PostgreSQL documentation, they gave C Syntax as client side
function.

Should I use those C API calls?

:)
Purusothaman A

On 9/11/06, Marco Bizzarri <marco.bizzarri@gmail.com> wrote:
>
> 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 object).
>
> > select  lo_open(198705, 131072) ;
> lo_open
> ---------
>        0
> (1 row)
>
> (this is the file handler which you will use in the operations).
>
> > SELECT lowrite(0, 'aaaa');
> lowrite
> ---------
>        4
> (1 row)
>
> (you wrote 4 character in a large object)
>
> > select lo_close(0);
> lo_close
> ----------
>         0
> (1 row)
>
> (you closed the file).
>
> > commit ;
> COMMIT
>
> In this way, you created a new large object, and stored a string of 4
> bytes inside of it.
>
> Regards
> Marco
>
> On 9/11/06, Purusothaman A <purusothaman.a@gmail.com> wrote:
> > 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-----
> >
> >
> >
> >
>
>
> --
> Marco Bizzarri
> http://notenotturne.blogspot.com/
>

view thread (15+ messages)  latest in thread

Message-ID: <3650d0d50609110630p7c0fa6dfsb9dbc995f4406680@mail.gmail.com>
Permalink:  ../3650d0d50609110630p7c0fa6dfsb9dbc995f4406680@mail.gmail.com/
Also on:    postgresql.org/message-id/3650d0d50609110630p7c0fa6dfsb9dbc995f4406680@mail.gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: purusothaman.a@gmail.com, kleptog@svana.org, marco.bizzarri@gmail.com, milen@radev.net, pgsql-general@postgresql.org
  Subject: Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.
  In-Reply-To: <3650d0d50609110630p7c0fa6dfsb9dbc995f4406680@mail.gmail.com>
  References: <3650d0d50609090407j237bb710h9bde1675c773925d@mail.gmail.com> <edu8r6$k56$1@sea.gmane.org> <3650d0d50609090449q2aec1098xc3b62dd169de5843@mail.gmail.com> <20060909120613.GA10336@svana.org> <3650d0d50609110215j7361bc2dj55e6d7d73af1d07d@mail.gmail.com> <20060911093819.GA15769@svana.org> <3650d0d50609110257m7b216b27nabb8ae87f7852e2@mail.gmail.com> <20060911100336.GB16564@svana.org> <3650d0d50609110315uff51429n48e038dc6b9a482e@mail.gmail.com> <3f0d61c40609110356n53e6da12h26d54cb74f448263@mail.gmail.com> <3650d0d50609110630p7c0fa6dfsb9dbc995f4406680@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox