[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SF.net SVN: ledger-smb: [421] trunk/sql/legacy/Pg-upgrade-2.6.18-2.6.19.sql
- Subject: SF.net SVN: ledger-smb: [421] trunk/sql/legacy/Pg-upgrade-2.6.18-2.6.19.sql
- From: ..hidden..
- Date: Mon, 30 Oct 2006 22:19:49 -0800
Revision: 421
http://svn.sourceforge.net/ledger-smb/?rev=421&view=rev
Author: einhverfr
Date: 2006-10-30 22:19:48 -0800 (Mon, 30 Oct 2006)
Log Message:
-----------
Making Pg-upgrade-2.6.18-2.6.19.sql safe to use for now
Modified Paths:
--------------
trunk/sql/legacy/Pg-upgrade-2.6.18-2.6.19.sql
Modified: trunk/sql/legacy/Pg-upgrade-2.6.18-2.6.19.sql
===================================================================
--- trunk/sql/legacy/Pg-upgrade-2.6.18-2.6.19.sql 2006-10-31 05:42:52 UTC (rev 420)
+++ trunk/sql/legacy/Pg-upgrade-2.6.18-2.6.19.sql 2006-10-31 06:19:48 UTC (rev 421)
@@ -146,6 +146,10 @@
LOCK session in EXCLUSIVE MODE;
ALTER TABLE session ADD CONSTRAINT session_token_check check (length(token::text) = 32);
ALTER TABLE session ADD column user_id integer not null references users(id);
+
+-- comment this out when user db is working:
+ALTER TABLE session ALTER COLUMN user_id DROP NOT NULL;
+
LOCK users in EXCLUSIVE MODE;
CREATE TABLE users (id serial UNIQUE, username varchar(30) PRIMARY KEY);
COMMENT ON TABLE users 'username is the primary key because we don't want duplicate users';
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.