pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fabrice Scemama <fabrice.scemama@gesnet.net>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Java/JDBC/PGSQL Mailing List Archiver
Date: Sun, 24 Jan 1999 15:29:42 +0000
Message-ID: <36AB3C66.66BDC13D@gesnet.net> (raw)
References: <19990121200031.16915.rocketmail@send105.yahoomail.com>
	<l03110705b2d0aa56c795@[147.233.159.109]>

I globally agree with your points. Thanks for taking time
to write them for us.

If 1, 2, and 3 cannot be considered as essential -- we still
can backup the BLOBs, delete them, etc. with few programming
skills, 4 is very important.

So, as you put it, as far as Mailing List Archives are concerned,
bodies should be split, and attachments BLOBed.

Chavouah Tov!

Fabrice Scemama
Internet Developer too, but in France ;)

Herouth Maoz wrote:
> 
> At 2:05 +0200 on 22/1/99, Fabrice Scemama wrote:
> 
> > I'd rather not split text messages in 8k parts!
> > That's what BLOBS were designed for
> 
> Just to give you a few off points on BLOBs:
> 
> (1) They are not dumped with pg_dump, and you have to design your own
>     backup procedure for them, which you will be able to integrate later
>     with a dumped database.
> 
> (2) You can't display them in a casual psql query. I usually use psql
>     when I want to check something in my database. Storing the text in
>     split records would allow you to view the content in psql.
> 
> (3) Sometimes one needs to delete some data which was entered incorrectly
>     or as a result of a buggy implementation. If you want to delete a
>     large object you have to write a program. If you want to delete a
>     bunch of split text records, you only have to enter psql and issue
>     a DELETE statement in SQL.
> 
> (4) You can't search on large objects. Not even an unindexed search.
>     You have to retrieve every large object, and perform the search in
>     the front end. If you had it in split text records, you would be
>     able to search with LIKE or regexp.
> 
> Attachments are a different story. All of the above applies when we are
> dealing with text processing. If the content is something other than text,
> you don't need to search it, there is no point in viewing it in PSQL
> because you need a proper viewer anyway, etc.
> 
> So if you want to treat your attachments as binary objects, binary objects
> they should be.
> 
> Herouth
> 
> --
> Herouth Maoz, Internet developer.
> Open University of Israel - Telem project
> http://telem.openu.ac.il/~herutma






view thread (7+ messages)  latest in thread

Message-ID: <36AB3C66.66BDC13D@gesnet.net>
Permalink:  ../36AB3C66.66BDC13D@gesnet.net/
Also on:    postgresql.org/message-id/36AB3C66.66BDC13D@gesnet.net

 · 

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: fabrice.scemama@gesnet.net
  Subject: Re: [SQL] Java/JDBC/PGSQL Mailing List Archiver
  In-Reply-To: <36AB3C66.66BDC13D@gesnet.net>
  References: <19990121200031.16915.rocketmail@send105.yahoomail.com> <l03110705b2d0aa56c795@[147.233.159.109]> <36AB3C66.66BDC13D@gesnet.net>

* 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