6.0.0-beta1
7/8/25

[#9171] scripts/sql/create.pgsql.sql doesn't create "horde_locks" table with the required "lock_scope" column
Summary scripts/sql/create.pgsql.sql doesn't create "horde_locks" table with the required "lock_scope" column
Queue Horde Base
Queue Version 3.3.8
Type Bug
State Resolved
Priority 1. Low
Owners slusarz (at) horde (dot) org
Requester lstewart (at) room52 (dot) net
Created 08/11/2010 (5445 days ago)
Due
Updated 08/12/2010 (5444 days ago)
Assigned
Resolved 08/12/2010 (5444 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
08/12/2010 07:57:15 PM Michael Slusarz Comment #3
Assigned to Michael Slusarz
State ⇒ Resolved
Reply to this comment
Fixed in Horde 3.3.9 and git master.
08/12/2010 07:56:38 PM CVS Commit Comment #2 Reply to this comment
Changes have been made in CVS for this ticket:

Bug: 9171
Merge from git master 8bba53e746c0db1ec83e98ea1287f39169bef44e
http://cvs.horde.org/diff.php/horde/scripts/sql/create.pgsql.sql?rt=horde&r1=1.1.10.24&r2=1.1.10.25&ty=u
08/11/2010 07:05:08 AM lstewart (at) room52 (dot) net Comment #1
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ scripts/sql/create.pgsql.sql doesn't create "horde_locks" table with the required "lock_scope" column
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
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.

Saved Queries