Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | lookups impl | Bryan Newbold | 2018-12-14 | 1 | -4/+4 |
| | |||||
* | implement new controlled vocabularies | Bryan Newbold | 2018-11-14 | 1 | -2/+2 |
| | |||||
* | fix isbn13 size check (!) | Bryan Newbold | 2018-09-22 | 1 | -2/+2 |
| | |||||
* | container_name (not title), and shrink some BIGINTs | Bryan Newbold | 2018-09-22 | 1 | -4/+4 |
| | |||||
* | fix CHECK clauses | Bryan Newbold | 2018-09-17 | 1 | -7/+7 |
| | |||||
* | UNIQUE constraint on edits (ident per editgroup) | Bryan Newbold | 2018-09-17 | 1 | -15/+10 |
| | |||||
* | use timestamptz (not WITHOUT TIME ZONE) | Bryan Newbold | 2018-09-17 | 1 | -8/+10 |
| | |||||
* | CHAR/VARCHAR -> TEXT w/ CHECK | Bryan Newbold | 2018-09-17 | 1 | -15/+28 |
| | |||||
* | update extid columns: varchar size limits, no char columns | Bryan Newbold | 2018-09-15 | 1 | -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 JSON | Bryan Newbold | 2018-09-10 | 1 | -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 branch | Bryan Newbold | 2018-09-10 | 1 | -0/+2 |
| | |||||
* | remove 'IS NOT NULL' identifier index constraints | Bryan Newbold | 2018-09-10 | 1 | -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 schema | Bryan Newbold | 2018-08-20 | 1 | -4/+4 |
| | |||||
* | add index on release_rev_abstract SHA1 column | Bryan Newbold | 2018-08-19 | 1 | -0/+1 |
| | |||||
* | add index on file_rev_url file_rev | Bryan Newbold | 2018-08-19 | 1 | -0/+2 |
| | |||||
* | create index on release_rev_abstracts | Bryan Newbold | 2018-08-18 | 1 | -0/+2 |
| | |||||
* | add core_id to schemas | Bryan Newbold | 2018-08-14 | 1 | -4/+6 |
| | |||||
* | contribs: raw -> raw_name | Bryan Newbold | 2018-07-25 | 1 | -3/+3 |
| | |||||
* | tweaks/fixes to SQL changes | Bryan Newbold | 2018-07-24 | 2 | -7/+10 |
| | |||||
* | bunch of SQL updates | Bryan Newbold | 2018-07-23 | 1 | -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 stub | Bryan Newbold | 2018-07-20 | 1 | -8/+4 |
| | |||||
* | update schema (sql and api) for rev ids, editor_id, editgroup_id | Bryan Newbold | 2018-07-20 | 1 | -113/+112 |
| | |||||
* | prep for base32 encoded identifiers | Bryan Newbold | 2018-07-20 | 1 | -17/+17 |
| | |||||
* | fix problems with dummy data | Bryan Newbold | 2018-06-30 | 1 | -9/+9 |
| | |||||
* | add some container extra_json to examples | Bryan Newbold | 2018-06-30 | 1 | -4/+4 |
| | |||||
* | add a bunch of database indexes | Bryan Newbold | 2018-06-27 | 1 | -0/+37 |
| | |||||
* | ISO 639-1 for language codes | Bryan Newbold | 2018-06-19 | 1 | -1/+1 |
| | |||||
* | change release field order, and larger examples | Bryan Newbold | 2018-06-17 | 1 | -20/+44 |
| | |||||
* | more consistent example data | Bryan Newbold | 2018-06-17 | 1 | -6/+6 |
| | |||||
* | updates to schema(s): more complete, alignment | Bryan Newbold | 2018-06-04 | 1 | -16/+27 |
| | |||||
* | renumber dummy/example entities | Bryan Newbold | 2018-05-28 | 1 | -29/+29 |
| | |||||
* | tweak schema (api and sql) | Bryan Newbold | 2018-05-26 | 1 | -16/+23 |
| | |||||
* | return all edits for an editgroup GET | Bryan Newbold | 2018-05-25 | 1 | -10/+10 |
| | |||||
* | index for contribs | Bryan Newbold | 2018-05-25 | 1 | -5/+6 |
| | |||||
* | more inserts; also fix typo around target_release_ident_id | Bryan Newbold | 2018-05-25 | 1 | -10/+57 |
| | |||||
* | revision publish date as Date | Bryan Newbold | 2018-05-24 | 1 | -2/+3 |
| | |||||
* | extra_json in SQL schema and implementation | Bryan Newbold | 2018-05-24 | 1 | -10/+10 |
| | |||||
* | more i64 cleanup | Bryan Newbold | 2018-05-24 | 1 | -2/+2 |
| | |||||
* | WIP on API spec improvements | Bryan Newbold | 2018-05-24 | 1 | -1/+1 |
| | | | | Fixes a bunch of i64/i32/isize stuff | ||||
* | move dummy data into primary migration | Bryan Newbold | 2018-05-24 | 3 | -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 Newbold | 2018-05-16 | 1 | -1/+1 |
| | |||||
* | simplify SQL schema a bit | Bryan Newbold | 2018-05-16 | 1 | -3/+5 |
| | |||||
* | remove all extra_json for now | Bryan Newbold | 2018-05-15 | 1 | -11/+11 |
| | |||||
* | include dummy data by default | Bryan Newbold | 2018-05-15 | 2 | -0/+59 |
| | |||||
* | JSONB back to JSON, and skip for container_rev while debugging | Bryan Newbold | 2018-05-15 | 1 | -11/+11 |
| | |||||
* | update schema | Bryan Newbold | 2018-05-15 | 1 | -8/+8 |
| | |||||
* | set correct primary keys on many-to-many tables | Bryan Newbold | 2018-05-15 | 1 | -3/+3 |
| | |||||
* | JSONB not JSON | Bryan Newbold | 2018-05-15 | 1 | -11/+11 |
| | |||||
* | diesel wants primary keys | Bryan Newbold | 2018-05-15 | 1 | -0/+2 |
| | |||||
* | tweaks to SQL schema | Bryan Newbold | 2018-05-14 | 1 | -3/+3 |
| |