phabricator/resources/sql/patches/078.nametoken.sql

CREATE TABLE {$NAMESPACE}_user.user_nametoken (
  token VARCHAR(255) NOT NULL,
  userID INT UNSIGNED NOT NULL,
  KEY (token(128)),
  key (userID)
) ENGINE=InnoDB;
SQL Patch Management: SQL Changes Summary: Splits out the SQL changes. These are most of the changes, but primarily mechanical: - Moved "initialize.sql" to "0000.legacy.sql" and partially reverted to an older version, such that patches 0000 + 000 + 001 + ... + 137 put us in the right state when applied sequentially. - Removed "create database" commands from all SQL. These are handled by separate DB patches now, so we have the data to do operations like "storage databases" (list databases) and "storage destroy" (drop databases). - Removed "phabricator_" namespace from all SQL, and replaced with "{$NAMESPACE}_" token so we can namespace databases. - Shortened some column lengths so patches apply correctly if originally created as InnoDB; also a few similar tweaks elsewhere. Test Plan: See D2323 for discussion and test plan. Reviewers: edward, vrana, btrahan, jungejason Reviewed By: btrahan CC: aran Maniphest Tasks: T140, T345 Differential Revision: https://secure.phabricator.com/D2329 2012-04-30 07:53:53 -07:00			`CREATE TABLE {$NAMESPACE}_user.user_nametoken (`
Add a name token table so on-demand typeaheads can match last names Summary: See T585. We currently don't match middle/last/nth names in on-demand tokenizers. Build a table so we can match them. Test Plan: Ran upgrade script, verified table looks sensible. Searched for "priestley" in a tokenizer, got a bunch of test account hits. mysql> select * from user_nametoken; +-------------------+--------+ \| token \| userID \| +-------------------+--------+ \| evan \| 1 \| \| priestley \| 1 \| \| epriestley \| 1 \| \| epriestley2 \| 2 \| \| ducks \| 4 \| \| epriestley3 \| 4 \| \| asdf \| 6 \| \| epriestley99 \| 6 \| ... Reviewers: bh, nh, jungejason, tuomaspelkonen, aran Reviewed By: aran CC: aran Differential Revision: 1034 2011-10-23 13:25:52 -07:00			`token VARCHAR(255) NOT NULL,`
			`userID INT UNSIGNED NOT NULL,`
Regenerate Quickstart SQL Summary: One advantage I wanted to get out of T1191 is automated rebuilds of `quickstart.sql`. If they don't actually work, I'd like to know sooner rather than later. We haven't rebuilt in a couple months, so give it a shot. Ran into two issues: - Some very old patches specify overlong keys which don't work if your default charsets are utf8mb4. Shorten these. No real users have applied these in a very long time. - Some gymnastics around `corpus` for the new Conpherence search index. Test Plan: - Ran `arc unit --everything`, got clean results. - Cost to do a storage upgrade on an empty namespace dropped from ~4s to ~3s. Reviewers: btrahan Reviewed By: btrahan Subscribers: epriestley Differential Revision: https://secure.phabricator.com/D11454 2015-01-22 16:10:26 -08:00			`KEY (token(128)),`
Add a name token table so on-demand typeaheads can match last names Summary: See T585. We currently don't match middle/last/nth names in on-demand tokenizers. Build a table so we can match them. Test Plan: Ran upgrade script, verified table looks sensible. Searched for "priestley" in a tokenizer, got a bunch of test account hits. mysql> select * from user_nametoken; +-------------------+--------+ \| token \| userID \| +-------------------+--------+ \| evan \| 1 \| \| priestley \| 1 \| \| epriestley \| 1 \| \| epriestley2 \| 2 \| \| ducks \| 4 \| \| epriestley3 \| 4 \| \| asdf \| 6 \| \| epriestley99 \| 6 \| ... Reviewers: bh, nh, jungejason, tuomaspelkonen, aran Reviewed By: aran CC: aran Differential Revision: 1034 2011-10-23 13:25:52 -07:00			`key (userID)`
			`) ENGINE=InnoDB;`