Arnaud, On Fri, Jan 26, 2018 at 7:34 AM, Arnaud de Montard via 4D_Tech < [email protected]> wrote: > > > Le 26 janv. 2018 à 15:55, Kirk Brooks via 4D_Tech <[email protected]> > a écrit : > > Even if you use the 'store outside of datafile' option the backups still > include the physical files. > > Some field options would make it better: > • don't load with record (something like a command 'External field load') > My understanding is this is the way it works already. Have you seen otherwise?
> • exclude from backup (very easy IMHO) > > I thought about this too and concluded it's probably not a good idea. The reason being it creates two 'classes' of data and that's not good. If something is part of the datafile then it's a full citizen and treated accordingly. To create this second class of data, which may or may not be backed up and therefore may or may not be accurate introduces a lot of complexity to the idea of a 'backup' and makes it impossible to guarantee a restore is accurate. I think the 'store outside the datafile' option is mis-used if you don't want it backed up. So the sorts of solutions we are discussing really are the better approach. I don't recall where but at some point I was part of conversation with someone from 4D talking about this external storage option and the idea for it was all about improving query speed - which is why I say I believe the external data are not returned with the record unless you reference that field directly. It's not about storage optimization but query optimization. Kirk Brooks San Francisco, CA ======================= *We go vote - they go home* ********************************************************************** 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:[email protected] **********************************************************************
