1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-12-15 18:10:53 +01:00
phorge-phorge/resources/sql/autopatches/20161005.cal.02.export.sql
epriestley 49448a87c1 Rough in most of Calendar exports
Summary:
Ref T10747. Rough flow is:

  - Run a query.
  - Select a new "Export Events..." action.
  - This lets you define an "Export", which has a unique URL you can paste into Google Calendar or Calendar.app or whatever.

Most of this does nothing yet but here's the boilerplate.

Test Plan: Doesn't do anything yet.

Reviewers: chad

Reviewed By: chad

Maniphest Tasks: T10747

Differential Revision: https://secure.phabricator.com/D16675
2016-10-06 04:06:35 -07:00

14 lines
591 B
SQL

CREATE TABLE {$NAMESPACE}_calendar.calendar_export (
id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,
phid VARBINARY(64) NOT NULL,
name LONGTEXT NOT NULL COLLATE {$COLLATE_TEXT},
authorPHID VARBINARY(64) NOT NULL,
policyMode VARCHAR(64) NOT NULL COLLATE {$COLLATE_TEXT},
queryKey VARCHAR(64) NOT NULL COLLATE {$COLLATE_TEXT},
secretKey BINARY(20) NOT NULL,
isDisabled BOOL NOT NULL,
dateCreated INT UNSIGNED NOT NULL,
dateModified INT UNSIGNED NOT NULL,
KEY `key_author` (authorPHID),
UNIQUE KEY `key_secret` (secretKey)
) ENGINE=InnoDB, COLLATE {$COLLATE_TEXT};