aboutsummaryrefslogtreecommitdiffstats
path: root/rust/migrations
Commit message (Collapse)AuthorAgeFilesLines
* ensure no zero-length strings in SQL schemaBryan Newbold2019-01-231-43/+43
|
* add missing arxiv+jstor id indicesBryan Newbold2019-01-221-0/+2
|
* SQL schema bumpBryan Newbold2019-01-211-9/+12
|
* sql schema: cdx timestamps as datetimeBryan Newbold2019-01-181-7/+7
|
* SQL schema PG version noteBryan Newbold2019-01-171-1/+2
|
* SQL schema for interned ref JSON blobsBryan Newbold2019-01-112-26/+36
|
* fix fcid note in SQL schemaBryan Newbold2019-01-111-1/+1
|
* fix some SQL meta-schema things (eg, richer examples)Bryan Newbold2019-01-112-7/+14
|
* minor SQL schema tweaks (column order and extra indexes)Bryan Newbold2019-01-111-3/+4
|
* SQL for annotations; editgroup is_accepted flagBryan Newbold2019-01-101-1/+16
| | | | is_accepted won't be implemented, much, for a bit.
* start removing active editgroup codeBryan Newbold2019-01-091-6/+2
|
* rename diesel migrations folder nameBryan Newbold2019-01-082-0/+0
|
* bump allowed username length to 25 charsBryan Newbold2019-01-071-1/+1
|
* only superusers get auto-magic-privsBryan Newbold2019-01-071-1/+1
|
* add superuser role/flagBryan Newbold2019-01-041-7/+8
|
* better username constraints in SQLBryan Newbold2019-01-031-1/+3
|
* OIDC auth table, and is_active editor flagBryan Newbold2019-01-032-0/+13
|
* make admin auth_epoch old so test tokens don't expireBryan Newbold2018-12-311-4/+4
|
* sql: add index on editor usernameBryan Newbold2018-12-271-0/+1
|
* first attempt at auth in DB schemaBryan Newbold2018-12-261-1/+4
|
* schemas: editor_id as UUID (not int)Bryan Newbold2018-12-261-7/+7
|
* webcapture: status_code nullable; cdx timestamp stringBryan Newbold2018-12-261-2/+2
|
* most basic fileset/web access testsBryan Newbold2018-12-261-6/+6
|
* basic fileset/web SQL entitiesBryan Newbold2018-12-261-0/+58
|
* sql: table deletion updatesBryan Newbold2018-12-261-1/+15
|
* sql: fixes to fileset/web; *_rev_releaseBryan Newbold2018-12-261-21/+21
| | | | | Several "ENTITY_release" tables renamed to "ENTITY_rev_release" for consistency.
* sql: size_bytes (size is a keyword)Bryan Newbold2018-12-261-2/+2
|
* fileset and webcapture SQL schemasBryan Newbold2018-12-241-1/+115
|
* implement release_year (and rustfmt)Bryan Newbold2018-12-241-4/+5
|
* ident table redirect lookupsBryan Newbold2018-12-201-0/+5
|
* lookups implBryan Newbold2018-12-141-4/+4
|
* implement new controlled vocabulariesBryan Newbold2018-11-141-2/+2
|
* fix isbn13 size check (!)Bryan Newbold2018-09-221-2/+2
|
* container_name (not title), and shrink some BIGINTsBryan Newbold2018-09-221-4/+4
|
* fix CHECK clausesBryan Newbold2018-09-171-7/+7
|
* UNIQUE constraint on edits (ident per editgroup)Bryan Newbold2018-09-171-15/+10
|
* use timestamptz (not WITHOUT TIME ZONE)Bryan Newbold2018-09-171-8/+10
|
* CHAR/VARCHAR -> TEXT w/ CHECKBryan Newbold2018-09-171-15/+28
|
* update extid columns: varchar size limits, no char columnsBryan Newbold2018-09-151-15/+15
| | | | | | | | | | | | In PostgreSQL, there is no query or size differences between CHAR, VARCHAR, and TEXT: they use the same backend. CHAR will pad out with spaces and VARCHAR enforces a size limit. The enforced VARCHAR size limit seems like ok defensive programming/schema here, preventing large values from getting stored for some columns. I have some FUD concern about fixed-sized identifiers and indexes, so switching old CHARs (eg, sha1 hex encoded columns) to VARCHAR instead.
* use JSONB over JSONBryan Newbold2018-09-101-13/+13
| | | | | | Sort of an impulsive "why not" decision. From earlier tests, expect this to consume a few % more disk (but not index)... adds a lot more query flexibility if we want that in the future. Seems worth the price.
* sql: add an index from cockroach branchBryan Newbold2018-09-101-0/+2
|
* remove 'IS NOT NULL' identifier index constraintsBryan Newbold2018-09-101-14/+14
| | | | | | | | | | | These seemed to be resulting in table scans on 404s in QA with postgres 10, despite the adding "IS NOT NULL" WHERE clauses earlier. Query time was very significant, even for the creator table (1.2 seconds or so on SSD). I looked at using hash indices (which have improved in postgres 10), which could save index size (disk and RAM) and potentially be faster for these trivial exact lookups, but didn't go for it at this time.
* use index_val, not index, in SQL schemaBryan Newbold2018-08-201-4/+4
|
* add index on release_rev_abstract SHA1 columnBryan Newbold2018-08-191-0/+1
|
* add index on file_rev_url file_revBryan Newbold2018-08-191-0/+2
|
* create index on release_rev_abstractsBryan Newbold2018-08-181-0/+2
|
* add core_id to schemasBryan Newbold2018-08-141-4/+6
|
* contribs: raw -> raw_nameBryan Newbold2018-07-251-3/+3
|
* tweaks/fixes to SQL changesBryan Newbold2018-07-242-7/+10
|
* bunch of SQL updatesBryan Newbold2018-07-231-48/+105
| | | | | | | | | - file urls as a table - more external identifiers (eg, pmcid, wikidata) - release ref and contrib mostly as JSON - abstracts - timestamps - fixed size external identifiers (CHAR not TEXT)
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-16 05:26:42 +0000