- January (Wednesday).
SQL Info
IBM tech support returned on my question about SQL updates from within Net.Data macros. It appears that doing such updates is fine (although we both felt a little leery of doing inserts). The net.data variable TRANSACTION_SCOPE controls how often database commits happen during a net.data macro execution. If set to "MULTIPLE" (default), any SQL error (including one from a SELECT) causes a rollback of everything done during that macro execution. If no error, a commit happens at the end of the macro execution.Alternately, setting the variable to "SINGLE" causes a commit after each UPDATE.
- January (Thursday).
I'm getting rather unhappy about how little is getting written down about this project -- algorithms, custom table specs, etc. etc. So I've started summarizing the data flow that happens in the shopping experience, if only to "lead by example". See Danly Shopping Experience: How it Works, also available as a link from my top IBS page.