One possible reason : VERSIONING.
The database makes it possible to store multiple instances of the same (or modified) object.
I have a perl app that takes weekly snapshots of all my network device configs. It compares the checksum of the current config to one in the database, and, if different, it stores the new config. This way, I can see when and how configs changed. By the way, the perl scripts that retrieve the config info are also stored in a database table - this allows me to use a master script to call a specific script for each specific device configured in the database (Yes, device name, IP etc is also stored in the database)
..."I don't know what the facts are but somebody's certainly going to sit down with him and find out what he knows that they may not know, and make sure he knows what they know that he may not know, and that's a good thing. I think it's a very constructive exchange," --Donald Rumsfeld
In reply to Re: literally saving a file inside a database
by NetWallah
in thread literally saving a file inside a database
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |