Task #2437
Story #2436: GMN, new features, bugfixes
Evaluate moving to database based locking
Start date:
2012-03-05
Due date:
% Done:
100%
Milestone:
None
Product Version:
Story Points:
Sprint:
Description
GMN currently uses thread based locking. This is fast and makes sense when GMN is used with a database with coarse grained locking, such as SQLite (which GMN was initially developed with). But when GMN is used with a more sophisticated database with fined grained locking, such as Postgres (and MySQL?), it would probably make sense use the database for locking. This would have the advantage of allowing an Apache configuration that runs GMN in multiple processes, and would avoid the potential issue of misconfigured Apache setups causing concurrency issues in GMN.
History
#1 Updated by Roger Dahl about 12 years ago
- Priority changed from Normal to Low
#2 Updated by Roger Dahl over 10 years ago
- Status changed from New to In Progress
- Priority changed from Low to Normal
#3 Updated by Roger Dahl over 10 years ago
- Status changed from In Progress to Closed
- translation missing: en.field_remaining_hours set to 0.0
Moved to database based locking.
