[Tickets #9171] scripts/sql/create.pgsql.sql doesn't create "horde_locks" table with the required "lock_scope" column
bugs at horde.org
bugs at horde.org
Wed Aug 11 07:05:08 UTC 2010
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/9171
------------------------------------------------------------------------------
Ticket | 9171
Created By | lstewart at room52.net
Summary | scripts/sql/create.pgsql.sql doesn't create
| "horde_locks" table with the required "lock_scope"
| column
Queue | Horde Base
Version | 3.3.8
Type | Bug
State | Unconfirmed
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
lstewart at room52.net (2010-08-11 03:05) wrote:
The script currently creates the table like so:
CREATE TABLE horde_locks (
lock_id VARCHAR(36) NOT NULL,
lock_owner VARCHAR(32) NOT NULL,
lock_principal VARCHAR(255) NOT NULL,
lock_origin_timestamp BIGINT NOT NULL,
lock_update_timestamp BIGINT NOT NULL,
lock_expiry_timestamp BIGINT NOT NULL,
lock_type SMALLINT NOT NULL,
PRIMARY KEY (lock_id)
);
It needs to include the "lock_scope" column like so:
CREATE TABLE horde_locks (
lock_id VARCHAR(36) NOT NULL,
lock_owner VARCHAR(32) NOT NULL,
lock_scope VARCHAR(32) NOT NULL,
lock_principal VARCHAR(255) NOT NULL,
lock_origin_timestamp BIGINT NOT NULL,
lock_update_timestamp BIGINT NOT NULL,
lock_expiry_timestamp BIGINT NOT NULL,
lock_type SMALLINT NOT NULL,
PRIMARY KEY (lock_id)
);
Postgres logs errors when the wrong schema is used.
The bug also appears to exist in the Git master branch.
More information about the bugs
mailing list