OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: SQL Mail Delivery Options
From: Greg Stark (gsstarkmit.edu)
Date: Sat Apr 01 2000 - 10:27:25 CST

"Jason Hoos" <jhoosthwack.net> writes:

> Only if you try to write the whole BLOB to the database at once, which is
> painful; most databases provide APIs for dealing with BLOBs in a piecemeal
> fashion to get around this problem.

Alternatively you could do that awful hack of avoiding BLOBS by using several
rows of varchars. This has the advantage of allowing you to seek around in the
message and some other neat effects. But it's really awkward and would make
fetching and inserting the data slower I think.

I used to think this whole concept of storing a mail queue in a relational
database was bogus, but the more I think about it the more I think it might be
reasonable. We process a lot of incoming mail through filters that update the
database in various ways. It might be simpler to process them if the data were
already in the database.

update users set subscribed = 0 where userid in
 (select userid from mailbox where processed <> 1 and lower(subject) like '%unsubscribe%');

Hmmm. 

-- 
greg