Mmm.. filter goodness. Trying again with the required words: sql query
> ... along the lines of using the database as a pointer to the real file in
a
> normal filesystem that others have suggested.. may I add the idea of using
a
> 'hashed' directory structure such that you don't end up with an ob
On Thu, Sep 26, 2002 at 10:31:06AM +0100, Andrew Bryant wrote:
> We have 125 million smallish images (each one is tens of KB, produced by
> gene sequencing machines). Currently we store these in tarfiles and
> index the images (the offset in the tar file) using an Oracle
> database. Each tarfile
I would highly recommend a simple design:
1) Create a large filesystem on your drive(s) using ReiserFS (because of fast file
finding capabilities).
2) Create a table that has one entry per image with an auto_increment primary key.
3) Insert a new record every time you 'store' an image, grab the
DB table.
Dean.
> -Original Message-
> From: Andrew Bryant [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 26 September 2002 7:31 pm
> To: [EMAIL PROTECTED]
> Subject: Storing 100 million images in the database
>
>
> Hello all,
>
> This discussion appeared recently:
Hello all,
This discussion appeared recently:
>| Can I use MySQL to store pictures as part of a record?
>| Should I just try to store the name of the picture?
>Yep but it depends on the size of the pictures.
Let me describe a scenario we have here in genomics research, which is
extremely deman
