aboutsummaryrefslogtreecommitdiffstats
path: root/rust/migrations
Commit message (Collapse)AuthorAgeFilesLines
* 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)
* sql: work really an empty stubBryan Newbold2018-07-201-8/+4
|
* update schema (sql and api) for rev ids, editor_id, editgroup_idBryan Newbold2018-07-201-113/+112
|
* prep for base32 encoded identifiersBryan Newbold2018-07-201-17/+17
|
* fix problems with dummy dataBryan Newbold2018-06-301-9/+9
|
* add some container extra_json to examplesBryan Newbold2018-06-301-4/+4
|
* add a bunch of database indexesBryan Newbold2018-06-271-0/+37
|
* ISO 639-1 for language codesBryan Newbold2018-06-191-1/+1
|
* change release field order, and larger examplesBryan Newbold2018-06-171-20/+44
|
* more consistent example dataBryan Newbold2018-06-171-6/+6
|
* updates to schema(s): more complete, alignmentBryan Newbold2018-06-041-16/+27
|
* renumber dummy/example entitiesBryan Newbold2018-05-281-29/+29
|
* tweak schema (api and sql)Bryan Newbold2018-05-261-16/+23
|
* return all edits for an editgroup GETBryan Newbold2018-05-251-10/+10
|
* index for contribsBryan Newbold2018-05-251-5/+6
|
* more inserts; also fix typo around target_release_ident_idBryan Newbold2018-05-251-10/+57
|
* revision publish date as DateBryan Newbold2018-05-241-2/+3
|
* extra_json in SQL schema and implementationBryan Newbold2018-05-241-10/+10
|
* more i64 cleanupBryan Newbold2018-05-241-2/+2
|
* WIP on API spec improvementsBryan Newbold2018-05-241-1/+1
| | | | Fixes a bunch of i64/i32/isize stuff
* move dummy data into primary migrationBryan Newbold2018-05-243-59/+62
| | | | | I couldn't come up with a "safe" way to wipe these rows (without causing larger insert PK uniqueness errors)
* unique usernames!Bryan Newbold2018-05-161-1/+1
|
* simplify SQL schema a bitBryan Newbold2018-05-161-3/+5
|
* remove all extra_json for nowBryan Newbold2018-05-151-11/+11
|
* include dummy data by defaultBryan Newbold2018-05-152-0/+59
|
* JSONB back to JSON, and skip for container_rev while debuggingBryan Newbold2018-05-151-11/+11
|
* update schemaBryan Newbold2018-05-151-8/+8
|
* set correct primary keys on many-to-many tablesBryan Newbold2018-05-151-3/+3
|
* JSONB not JSONBryan Newbold2018-05-151-11/+11
|
* diesel wants primary keysBryan Newbold2018-05-151-0/+2
|
* tweaks to SQL schemaBryan Newbold2018-05-141-3/+3
|
* flesh out SQL schemaBryan Newbold2018-05-142-3/+166
|
* add scratch rust stuffBryan Newbold2018-05-134-0/+111
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-11 18:45:08 +0000