NEXTID file is fragile (ITS#141)

[dave@chello.com]

Full_Name: David Boyce
Version: 1.2 stable
OS: Solaris 2.6
URL: 
Submission from: (NULL) (212.83.65.232)


The NEXTID file is crucial to the operation of the database, but the update
procedure isn't failsafe. Writing a new nextid number isn't even an atomic
operation in itself, so there's the possibility of it containing a corrupt
value. The ldbm backend should use a better mechanism than
fopen/fprintf/fclose.

Perhaps this should be a consideration for the new db2 backend?