Project

General

Profile

Bug #3019

Remove usage of .lastid files within the registry

Added by Shaun Walbridge about 12 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
Normal
Category:
registry
Target version:
Start date:
11/28/2007
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3019

Description

The registry currently relies on a .lastid file residing within the skin folder for each skin in use. This file is used to keep track of the last accession number used for insertion, but should be removed as it causes configuration issues: it sometimes must be manually seeded to be correct, it must be writable by the apache user, and it isn't thread-safe.

To replace the file, the server should always be queried through getLastDocid (getLastId in the Perl bindings) for the highest accession number within a given scope, and only use this canonical resource.

History

#1 Updated by Shaun Walbridge over 11 years ago

Fixed in r4378. Instead of storing the last used id (lastid) on disk, just perform a lookup each time, eliminating the pain-point of needing to set the permissions correctly on each .lastid file.

Removed updateLastId() function, consolidated everything under newAccessionNumber(). Rewrote the insertMetadata() call and associated 'updating' code accordingly. If conflicts do arise, we should fix them by changing things in getMaxDocId within DBUtil.java directly.

#2 Updated by Redmine Admin almost 7 years ago

Original Bugzilla ID was 3019

Also available in: Atom PDF