Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 0 additions & 29 deletions server/postgres/migrations/000000_initial.sql
Original file line number Diff line number Diff line change
Expand Up @@ -135,29 +135,6 @@ CREATE INDEX apikeysndvweifu_uid_idx ON apikeysndvweifu USING btree (uid);
CREATE INDEX apikeysndvweifu_apikey_idx ON apikeysndvweifu USING btree (apikey);






--CREATE TABLE orgs (
--oid SERIAL,
--oname VARCHAR(999)
--);

--CREATE TABLE oadmins (
--uid REFERENCES users(uid),
--oid REFERENCES orgs(oid),
--UNIQUE (uid, oid)
--);

--CREATE TABLE omemberships(
--oid REFERENCES orgs(oid),
--uid REFERENCES users(uid),
--UNIQUE (uid, oid)
--);

--CREATE TABLE org_member_metadata_types (

CREATE TABLE courses(
course_id SERIAL,
topic VARCHAR(1000),
Expand Down Expand Up @@ -502,12 +479,6 @@ CREATE TABLE suzinvites (
CREATE INDEX suzinvites_owner_zid_idx ON suzinvites USING btree (owner, zid);


--CREATE TABLE permissions(
--uid INTEGER NOT NULL REFERENCES users(uid),
--zid INTEGER NOT NULL REFERENCES conversations(zid),
--rwx?
--admin bool
--);


-- can't rely on SEQUENCEs since they may have gaps.. or maybe we can live with that? maybe we use a trigger incrementer like on the participants table? that would mean locking on a per conv basis, maybe ok for starters
Expand Down
Loading