pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Franck Martin <franck@sopac.org>
To: Jan Wieck <janwieck@Yahoo.com>
Cc: ohp@pyrenet.fr, Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: BLOB HOWTO??
Date: Tue, 30 Jan 2001 22:50:15 +1300
Message-ID: <3A768E57.375E8FF9@sopac.org> (raw)
References: <200101291914.OAA04385@jupiter.greatbridge.com>

I'm interested by TOAST, and I have asked several questions on the subject...
I haven't tested them yet...

First I thought that the type bytea allows storing of binary data, a BSOB
(Binary Small OBject).
Secondly that by using a binary cursor you have access to the raw data as it
is stored in the database, but not as it is presented in ASCII
Thridly we could use a funtion to retreive parts of columns, something like
mid(column,start,length)
Fourthly we may use the same function for storing data back.

Cheers...
Franck@sopac.org

Jan Wieck wrote:

> Olivier PRENANT wrote:
> > Hi Bruce,
> >
> > Any idea when it's due for??
> > I've been thining about writing a user function; But I'll get stuck with
> > permission as a user function is running under the "postgres" or whatever
> > user instead of the calling user.
> >
> > Also, what kind of binary interface are you thinking of??
>
>     Something similar to the existing lo_...() functions.
>
>     Actually,  someone  should  use the existing large objects to
>     deal with binary content.  What has to be kept in mind is
>
>     1.  You have to cleanup yourself - the existing large objects
>         aren't  removed  automatically  if you delete a table row
>         referencing to the LO or drop the table.
>
>     2.  The existing LOs don't have copy  behaviour.  So  if  you
>         reference  to  a  LO  from one table and do an INSERT ...
>         SELECT, just it's OID is copied,  not  the  data  (as  it
>         should be IMHO).
>
> Jan
>
> --
>
> #======================================================================#
> # It's easier to get forgiveness for being wrong than for being right. #
> # Let's break this rule - forgive me.                                  #
> #================================================== JanWieck@Yahoo.com #
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com




view thread (12+ messages)

Message-ID: <3A768E57.375E8FF9@sopac.org>
Permalink:  ../3A768E57.375E8FF9@sopac.org/
Also on:    postgresql.org/message-id/3A768E57.375E8FF9@sopac.org

 · 

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-sql@postgresql.org
  Cc: franck@sopac.org, janwieck@Yahoo.com, pgman@candle.pha.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: BLOB HOWTO??
  In-Reply-To: <3A768E57.375E8FF9@sopac.org>
  References: <200101291914.OAA04385@jupiter.greatbridge.com> <3A768E57.375E8FF9@sopac.org>

* 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