On 2/13/06, Cameron Childress <[EMAIL PROTECTED]> wrote: > On 2/13/06, David <[EMAIL PROTECTED]> wrote: > > Does the size of these files seem reasonable for 1, and 2 would be > > overkill? or would CF's list processing be too inefficient for that? > > If this only happens every so often, then performance really shouldn't > be the biggest worry for you. If it can be scheduled or setup as a > "fire and forget" on demand task I would go with whatever solution is > least fragile, has the least moving parts, and is easiest to maintain. > > If this process is going occur frequently of be fired off by a user > with time sensitivity you may want to look at performance - aside from > that I would focus on meaking it easy to maintain. > > -Cameron
"least fragile, has the least moving parts, and is easiest to maintain" makes a lot of sense. This is supposed to run whenever the host data changes; probably no more often than once in a few weeks, up to few months, whenever the group we're sending to gets notified of the change and requests it. Ideal would be to have it all happen programmatically on request, but doesn't require user to be waiting for it. We're also looking at how well the flat files map to the xml (someone else is doing a full comparison). The reason we thought of SQL as a temporary step is for parsing the files, and as temp storage and better retrieval in case we need to collect from multiple files for one section of the xml output. It seems like a fairly straightforward mapping though, except for the parent and child records in the same flat file. I'll do some tests tomorrow. Thanks, - David ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232183 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
