comment on

I'll probably end up going the route of putting the files on the disk. But it does have a slight snag (that our app currently does not deal with): if we ever need to reorganize the disk structure (which would be rare), we would need to ensure that the paths in the database are updated appropriately.

... Or (thinkig out loud), in our API layer, just provide a function that generates the filename the data would be stored under.

Storing the file in a RDBMS that supports cascadeing deletes is also handy -- when we delete the primary entry, the DBMS will also clobber the files automatically for us. W/ a disk-on-file approach, we have to run an off-line clean-up script that manually clobbers files for any deleted rows.

Even still, is there a way to bind a paramater to a filehandle, and have the driver figure out the details to get that file into the DB ?

In reply to Re: Storing files in a database by mystik
in thread Storing files in a database by mystik

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks