Ed wrote: > On Wednesday 07 March 2007 19:28, Jay Pipes wrote: >> Is there a specific reason you want to store this in a database? Why >> not use the local (or networked) file system and simply store the >> metadata about the PDF in the database? >> >> Cheers, >> >> Jay > > Hi Jay, > Could you explain what you mean by metadata and how you would do it? > Thanks > -Ed >
Pretty much you store all the info about the file (since this is billing maybe a billing number customer id etc) then you would reference a path to the file (could be just a name or a full path.) I've done this with images. Stored height, width and file name (along with an ID.) The file name was just that, no path (everything was relative to a 'main' images directory but you can lay it out however you like.) This is usually easier on web apps to do this. You don't have gobs of info in a db, and anybody can backup/restore files. I can see other reasons not to keep them on a file system and on a DB (like cross site) but even then, with the proper replication scheme that can be worked out as well. -- Thanks, James -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
