Re: Let me be the first

> Let's think about this for a second. Person A is doing a batch routine > that has to process every customer account in a branch (say branch X). > Person B is doing interactive queries for random customers, some of which > may be in branch X. > No, peresn A runs a process for clients of branch X and person B reads clients of branch Y! Users own their data and run batch processing on them (in background threads). > Let's say that Person B is looking into the details for Customer 123, who > happens to bank at branch X. > > If person A is currently processing customer 123, then it's only right > that person B can't see the rows for customer 123. But if person A is > processing some other customer's data, then I can't really see why the > data for customer 123 should be locked. > > Why would the data for customer 123 be locked? > All the processing is done in one transaction becase of consistency with data in the datamart (tables with clients, accounts, etc.). Lukas

Lukas Barton wrote: > > Let's think about this for a second. Person A is doing a batch routine > > that has to process every customer account in a branch (say branch X). > > Person B is doing interactive queries for random customers, some of which > > may be in branch X. > > > No, peresn A runs a process for clients of branch X and person B reads > clients of branch Y! > Users own their data and run batch processing on them (in background > threads). > > Let's say that Person B is looking into the details for Customer 123, who > > happens to bank at branch X. > > > > If person A is currently processing customer 123, then it's only right > > that person B can't see the rows for customer 123. But if person A is > > processing some other customer's data, then I can't really see why the > > data for customer 123 should be locked. > > > > Why would the data for customer 123 be locked? > > > All the processing is done in one transaction becase of consistency with > data in the datamart (tables with clients, accounts, etc.). > > Lukas Ok the rows are locked becasue you choose them to be locked row versioning would let you read old data that has been changed dirty read would let you read new data that might not be committed would row versioning still let you update the row and then apply the change later?