I am pleased to announce the opening of Playing Fair, my partner’s Brisbane-based online store for fair trade children’s clothes. All of the garments are sourced through an importer recognised by the British Association of Fair Trade Shops (BAFTS).
Here’s a small sample of the products that are available:
Playing Fair was developed using 100% open source software, including Python, Satchmo, and runs on an Ubuntu Linux server.
I stumbled across this remark in some documentation for Intersystems Caché ObjectScript.
You use the Lock command to prevent multiple processes from updating the same record at the same time. But it only works by convention: all the code throughout an application that updates a given global must try to Lock the record that is to be updated, and unLock it when finished. If one routine uses Lock, but another doesn’t, nothing prevents the second routine from updating the record while the first routine has it locked.
Date: 2010-11-19 17:21:07 UTC
Author: Joe Bayus
Yes, it’s true, and always has been for M installations. One advantage is that it prevents someone from locking up entire nodes or huge sections of the data (locking a node locks all the entries “below” it) – it also requires a well-organized and coordinated system design to work properly. Always something worth encouraging, don’t you think?
Date: 2010-11-20 00:13:40 UTC
If locks aren’t quite locks, what happens to transactions?
Date: 2010-12-17 20:34:01 UTC
Author: Jim Volstad
A record (?) is locked and other jobs can still update it? OMG!