[CalendarServer-changes] [10260] CalendarServer/branches/users/glyph/queue-locking-and-timing

[source_changes at macosforge.org]

Revision: 10260
          http://trac.calendarserver.org//changeset/10260
Author:   glyph at apple.com
Date:     2013-01-04 16:39:22 -0800 (Fri, 04 Jan 2013)
Log Message:
-----------
NAMED_LOCK table as required by enterprise.locking.

Modified Paths:
--------------
    CalendarServer/branches/users/glyph/queue-locking-and-timing/txdav/common/datastore/sql_schema/current.sql

Property Changed:
----------------
    CalendarServer/branches/users/glyph/queue-locking-and-timing/

Modified: CalendarServer/branches/users/glyph/queue-locking-and-timing/txdav/common/datastore/sql_schema/current.sql
===================================================================
--- CalendarServer/branches/users/glyph/queue-locking-and-timing/txdav/common/datastore/sql_schema/current.sql	2013-01-05 00:39:21 UTC (rev 10259)
+++ CalendarServer/branches/users/glyph/queue-locking-and-timing/txdav/common/datastore/sql_schema/current.sql	2013-01-05 00:39:22 UTC (rev 10260)
@@ -38,7 +38,13 @@
   primary key (HOSTNAME, PORT)
 );
 
+-- Unique named locks.  This table should always be empty, but rows are
+-- temporarily created in order to prevent undesirable concurrency.
+create table NAMED_LOCK (
+    LOCK_NAME varchar(255) primary key
+);
 
+
 -------------------
 -- Calendar Home --
 -------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/calendarserver-changes/attachments/20130104/d2f9bf6e/attachment-0001.html>