John, I was initially excited about this external storage option for the same reasons: lots and lots of image files I needed to store and index and maybe have the option to edit via external programs (Photoshop or Pixels). This is not the real intent of the design though.
I think the goal for storing files externally is to speed up queries on those records. As I understand it when a sequential (non indexed) query is performed the entire record is loaded into memory. So not loading these big text/blob/picture fields instantly speeds up that process a lot. When folks like us look at it as a storage solution we're hacking it into something different. For me the biggest issue that instantly came up was the size of the backup files and the time they took to build. You don't (or didn't, I haven't checked recently) have an option to exclude external data from the backup. This makes sense from 4D's perspective because 4D has no way of distinguishing whether that data is super critical or not. Data is data so it backs it all up. Ultimately I went with a scheme where I index the documents in 4D and store them on AWS (and thanks again to Bruno LeGay for his excellent component for managing this sort of thing). For image files I store two versions: a thumbnail (300x300) and the full file. There's an argument for storing the thumbnail in the datafile. I choose not to and that's very likely just a matter of taste. Once it's on AWS getting the file is simplicity itself - you simply reference its URL. To store a changed copy you'll need to re-upload the new file. And it's cheap. You can use the cost calculator on AWS to work it out but I suspect it will cost less per month than you spent on coffee today plus you've got security options galore. Ping me offline if you'd like to do a phone call and I'll show you how I'm using it. On Sat, Jun 10, 2017 at 10:07 AM, John Baughman via 4D_Tech < 4d_tech@lists.4d.com> wrote: > As I read the docs, there is no way to have the .ExternalData folder > anyplace other than inside the database folder and still have 4D manage the > files. > > ... > > My question is, why can’t the path to the default folder be defined by the > developer or end user? > ... > > I don’t see why there couldn’t be a way to designate the location of the > default folder. Is there a way to do this now that I am missing? Is my > thinking flawed in some way? Perhaps this is a good idea for a feature > request? > -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************