If several flat file databases/tables are appended simultaneously across a network and/or volumes, is there a concurrency issue with ndex?
Yes, a lock agent will have to be implemented to avoid the phantom record problem. Although the lock agent itself is rather straight forward, the network/volume wide fault and exception handling is not. Bear in mind that ndex was implemented as a constant database, where updates are appended to the end of the database file, as is the usual case for financial time series databases. As an example of the complexity using semaphore locks, see dbappend in the dbappend.shar.gz archive.
