I posted a message about transactions and caching earlier today. I have an additional question.
If you have a series of calls dataset.begin … dataset.commit … dataset.begin … dataset.commit … Is it the case that the database state used within the first transaction is available to the subsequent transactions. Is a call to dataset.close cause all of this database state to be freed up and no longer associated with the dataset. When you make the call the second time to dataset.begin(), suppose another transaction had already committed a transaction involving updates. When the second transaction begins, will it then replace state the dataset is maintaining, with the newly committed updates? My goal here is how to properly maintain cached state, avoid the overhead of re-reading the database, redoing inferencing inside each transaction. David Jordan Senior Software Developer SAS Institute Inc. Health & Life Sciences, Research & Development Bldg R ▪ Office 4467 600 Research Drive ▪ Cary, NC 27513 Tel: 919 531 1233 ▪ [email protected]<mailto:[email protected]> www.sas.com<http://www.sas.com/> SAS® … THE POWER TO KNOW®
