On Thu, Jun 10, 2010 at 12:34 PM, Stefan Scott Alexander <[email protected]> wrote: > - Does J's column-oriented approach make it prohibitively inefficient to > have say several users simultaneously trying to add or edit rows in the same > table from separate workstations?
It might. > - Would J be simply inefficient in such a case - or could it also lead to > actual record contention errors - say problems generating unique ids for > each rows, or problems trying to simultaneously write multiple records to > the same table? The problem is efficiency, not locking. In essence everything is always locked. And, if you want efficiency, you should "batch up" user requests and process as many as you can in one go. That said, J is essentially implemented as a single thread in a single process. If you want concurrency, you need to implement multiple J programs. FYI, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
