|
|
Posted by Andy Hassall on 06/29/06 21:11
On 29 Jun 2006 12:45:34 -0700, "Richard Levasseur" <richardlev@gmail.com>
wrote:
>> to be os independent and easier backup of the running app.
>
>It is better practice to store a link in the DB and the file in the
>file system.
>
>Accessing the file is also faster, as it doesn't have to go through the
>database.
>
>Backing up shouldn't be an issue. Backups should be done by scripts,
>at the most you should only have to click a button or run a command to
>perform a back up.
When you just store filenames, there's no transactional link between the
metadata in the database, and separate files on the filesystem, so it makes
writing the backup system behind the button more complicated to implement
correctly, particularly during hot backups.
Sometimes storing the files in the database along with its metadata, making it
easier to make self-consistent backups amongst other factors, offsets the
overheads. As with most things, it depends on what you're actually doing.
--
Andy Hassall :: andy@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool
Navigation:
[Reply to this message]
|