Well, the thing is that the mp3's are stored in another computer and the
db is running in another one.
Those mp3 files are generated daily. The size of all daily mp3 is not so
huge. (~ 40 mega mp3 generation per day).
I think that to make them accessible through the web the best thing is
to
put them into the db.
However the idea of the relative path it is good too (in my opinion).
It is likely I will try both possibilities and then see what it will be
the more interesting.
Thank for every one who contributes to this question.
I wish all a good week-end
/JF
-----Urspr�ngliche Nachricht-----
Von: Christoph Hermann [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 19. Februar 2005 14:49
An: [email protected]
Betreff: Re: [MP3 to DB]: load - store
Mike Dickson schrieb:
Hello,
> Do not store the mp3-Files in the database.
> Store them in the Filesystem and insert the path to the Files into
> the Database.
> Then someone can rename a directory or two and then the fun starts.
> :-) Put them in the DB. Trust me.
No User should have the Right to do so.
If the User has the Right, then he should be responsible enough to
change the related entries in the database.
Also only relative paths are stored in the Database, so this is not
really a Problem.
Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
