On Apr 24, 2017, at 9:25 PM, Douglas von Roeder via 4D_Tech <[email protected]> wrote:
> Anyone here have experience with Brad Weber's "FTSY Sync" code? > > One aspect of the code that's challenging is that the V11+ code (the "new" > code) could no longer use 4D Open so the design was changed to pack field > data into BLOB's. The BLOB's contain metadata for every field including the > field number, the field type, the data length, etc. > > When the synch records are unpacked, the metadata is used to move > sequentially through the BLOB, converting each byte range back to its > native 4D type using BLOB to text, BLOB to real, BLOB to longint, etc. [snip] > The underlying question is how much faster/slower would it be to > encode/decode data using an alternative method? I wrote similar code a long time ago, and just replaced it last year (it stored the metadata in the resource fork, which was going to be problematic soon). Exports usually contained hundreds of records of 3-4 tables of 100+ fields, and when importing were parsed pretty much instantly. Unless the unpacking code is very very inefficient, it’s not likely to be the source of any noticeable slowness when compiled. Jim Crate ********************************************************************** 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] **********************************************************************
