mediawiki-extensions-Echo/db_patches/echo_push_provider.sql

-- Table for normalizing push providers; intended for use with the NameTableStore construct.
CREATE TABLE /*_*/echo_push_provider (
    epp_id TINYINT UNSIGNED NOT NULL PRIMARY KEY auto_increment,
    -- push provider name; expected values are 'fcm' and 'apns'
    epp_name TINYBLOB NOT NULL
) /*$wgDBTableOptions*/;
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62 2020-05-15 17:19:03 +00:00			`-- Table for normalizing push providers; intended for use with the NameTableStore construct.`
			`CREATE TABLE /_/echo_push_provider (`
push: send apns topic when present 1) send apns topic when present in subscription metadata 2) check if subscription metadata is a valid JSON string 3) make epp_id column at echo_push_provider table auto_increment, otherwise it will fail when trying to add a second row in the table Bug: T259394 Change-Id: I785435e9f2d4ba9c14977d431d271f0fa2d0c795 2020-08-03 18:27:47 +00:00			`epp_id TINYINT UNSIGNED NOT NULL PRIMARY KEY auto_increment,`
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62 2020-05-15 17:19:03 +00:00			`-- push provider name; expected values are 'fcm' and 'apns'`
Change echo_push_* column types from TEXT to BLOB Per DBA review feedback, BLOB is more commonly used and may be preferable. Bug: T246716 Change-Id: I499d8c548088453d3182174f6f035977e8802240 2020-09-14 19:00:28 +00:00			`epp_name TINYBLOB NOT NULL`
Add push subscription management Adds DB tables for storing push subscriptions, some DB interaction code for retrieving them within MediaWiki, and a set of API modules for managing them from the outside world. When testing this patch, be sure to run maintenance/update.php to create the new tables, and set $wgEchoEnablePush = true in LocalSettings.php to enable the API new API module. N.B. The current DB schema is centered on app push subscriptions. Web push subscriptions require slightly different handling, since they are provided by browsers as a JSON blob rather than a token string. How to handle web push subscriptions is a question we can defer until the time comes to add web push support. Subscription data is stored in the echo_push_subscription table, with provider names normalized into the echo_push_provider table. We expect to be looking up subscriptions by central user ID, so that column is indexed. The subscription data also includes a column to store SHA256 digests of the subscriber tokens. This is for use as a unique key constraint, since we expect every push token to be univerally unique, and the token values themselves may be too large to reasonably index in MySQL. Bug: T252899 Change-Id: I3928761b3fba12e54ff4850e9a05c68ec7772f62 2020-05-15 17:19:03 +00:00			`) /$wgDBTableOptions/;`