SQL

It seems like on Wed, May 10, 2000 at 08:49:07PM -0700, Austin Godber scribbled:
Orig Msg> On Wed, May 10, 2000 at 07:45:08PM -0700, J.L.Francois wrote:
Orig Msg> >
Orig Msg> ...
Orig Msg> > My current database is filled with MP3s and I currently get
Orig Msg> > performance in the range of 1Meg+/sec on selects.
Orig Msg>
Orig Msg> I've always wondered about this. Do you actually keep the MP3s in the
Orig Msg> database or just a path to the MP3s? I have recently collected a large
Orig Msg> number of text/ps/pdf and would like to somehow organize them where I
Orig Msg> could query Author, abstract, keyword, text maybe. So would it be best to
Orig Msg> just include links or hold the actual files in the DB?
Orig Msg>
Orig Msg> Oh, I know nothing about databases so I don't know if this is a stupid
Orig Msg> question or not.
Orig Msg>
Orig Msg> --
Orig Msg> Austin Godber
Orig Msg> godber@asu.edu
Orig Msg>


Good question.

I have all of my MP3s stored in my database.

I also have some other binary data in my database i
that I wrote some simple encrypt/decrypt routines for in Perl.
I still get greater than 1MEG/sec xfer rates even with
the overhead of Perl and the decryption routines on SELECTs.

I'm the paranoid one.
Stuff in the database is
easier to protect :)

Due to the nature of how ext2 works (slowly) with directories
full of files I get better performance reading them from the
database than from the filesystem.

I set up the system so that I could take any data of any type
from any source and feed it thru my "insert" script and
store it encrypted in the database for fast indexing/retrieval.
This is great for logs, binaries, web content, etc.

It was my MP3 project that gave me the practice.

=================================================================
SAMPLE - This table is generic enuff to handle most of my needs.
=================================================================

CREATE TABLE anyfile_data( serial      int4         NOT NULL,
                           recvd       varchar(255) NOT NULL,
                           lineid      int4         NOT NULL,
                           keywords    varchar(255) NOT NULL,
                           filename    varchar(255) NOT NULL,
                           anyfiledata varchar(255) NOT NULL,
                           mimetype    varchar(255) NOT NULL,
                           createdate  varchar(255) NOT NULL );
=================================================================

JLF Sends...

This message brought to you by General Necromancy:
     "At General Necromancy, we bring dead things to life."