Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | fiddle with test helper functions | Bryan Newbold | 2018-11-13 | 3 | -145/+180 |
| | |||||
* | start using client in some tests | Bryan Newbold | 2018-11-13 | 3 | -0/+69 |
| | |||||
* | set default host in swagger spec to api.fatcat.wiki | Bryan Newbold | 2018-11-13 | 4 | -3/+4 |
| | |||||
* | update codegen (trivial) | Bryan Newbold | 2018-11-12 | 3 | -116/+115 |
| | |||||
* | pv in line mode during exports | Bryan Newbold | 2018-10-12 | 1 | -1/+1 |
| | |||||
* | better default file names | Bryan Newbold | 2018-09-25 | 1 | -1/+1 |
| | |||||
* | fix isbn13 size check (!) | Bryan Newbold | 2018-09-22 | 1 | -2/+2 |
| | |||||
* | update export command | Bryan Newbold | 2018-09-22 | 1 | -1/+1 |
| | |||||
* | rustfmt, and implement schema tweaks | Bryan Newbold | 2018-09-22 | 6 | -105/+75 |
| | |||||
* | container_name (not title), and shrink some BIGINTs | Bryan Newbold | 2018-09-22 | 1 | -4/+4 |
| | |||||
* | codegen fatcat-api-spec | Bryan Newbold | 2018-09-22 | 10 | -2809/+2979 |
| | |||||
* | squelch diesel macro warnings | Bryan Newbold | 2018-09-18 | 2 | -0/+4 |
| | |||||
* | fatcat-export rustfmt | Bryan Newbold | 2018-09-17 | 1 | -28/+50 |
| | |||||
* | re-generate database_schema.rs | Bryan Newbold | 2018-09-17 | 1 | -23/+23 |
| | |||||
* | fix CHECK clauses | Bryan Newbold | 2018-09-17 | 3 | -22/+23 |
| | |||||
* | 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 |
| | |||||
* | remove is_not_null redundant lookup conditions | Bryan Newbold | 2018-09-15 | 1 | -12/+0 |
| | |||||
* | 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. | ||||
* | remove duplicate response def from API spec | Bryan Newbold | 2018-09-13 | 1 | -4/+0 |
| | |||||
* | add missing fatcat-api-spec .gitignore | Bryan Newbold | 2018-09-13 | 1 | -0/+2 |
| | |||||
* | switch to new null (not \N) dump format | Bryan Newbold | 2018-09-13 | 1 | -4/+4 |
| | |||||
* | fix rust in-line tests, and parse_line takes ref | Bryan Newbold | 2018-09-12 | 2 | -7/+7 |
| | | | | Forgot to run tests before pushing... thanks CI! | ||||
* | need to specify binary for 'cargo run' now | Bryan Newbold | 2018-09-12 | 2 | -2/+2 |
| | |||||
* | rust/TODO update | Bryan Newbold | 2018-09-12 | 1 | -11/+1 |
| | |||||
* | improvements to fatcat-export output | Bryan Newbold | 2018-09-11 | 4 | -24/+136 |
| | |||||
* | improvements to fatcat-export | Bryan Newbold | 2018-09-11 | 3 | -29/+80 |
| | |||||
* | use idiomatic from_str for ExpandFlags | Bryan Newbold | 2018-09-11 | 2 | -14/+18 |
| | |||||
* | more subtle local ident check in release.db_expand() | Bryan Newbold | 2018-09-11 | 1 | -4/+4 |
| | |||||
* | first pass fast export | Bryan Newbold | 2018-09-11 | 4 | -1/+335 |
| | |||||
* | implement new editgroup_id behavior | Bryan Newbold | 2018-09-11 | 13 | -249/+458 |
| | |||||
* | refactor entity get and 'expansion' | Bryan Newbold | 2018-09-11 | 3 | -81/+64 |
| | |||||
* | derive PartialEq for FatCatId | Bryan Newbold | 2018-09-11 | 1 | -1/+1 |
| | |||||
* | add ExpandFlags type | Bryan Newbold | 2018-09-11 | 1 | -0/+72 |
| | |||||
* | finish fatcat-api => fatcat-api-spec refactor | Bryan Newbold | 2018-09-11 | 8 | -17/+17 |
| | |||||
* | fix fatcat-api-spec deps | Bryan Newbold | 2018-09-11 | 2 | -6/+6 |
| | |||||
* | new rustfmt | Bryan Newbold | 2018-09-11 | 2 | -26/+35 |
| | |||||
* | refactor fatcat-api => fatcat-api-spec | Bryan Newbold | 2018-09-11 | 22 | -64/+109 |
| | |||||
* | update TODO lists (september plan) | Bryan Newbold | 2018-09-11 | 1 | -16/+31 |
| | |||||
* | rust clippy (lint) tweaks | Bryan Newbold | 2018-09-11 | 4 | -14/+15 |
| | |||||
* | use JSONB over JSON | Bryan Newbold | 2018-09-10 | 2 | -26/+26 |
| | | | | | | 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 |
| | |||||
* | update TODO | Bryan Newbold | 2018-09-10 | 1 | -8/+2 |
| | |||||
* | many small API cleanups | Bryan Newbold | 2018-09-10 | 5 | -193/+148 |
| | | | | | | - use FatCatId much more often (though not everywhere yet) - more consistent types - remove redundant error handling code in wrappers | ||||
* | re-gen rust code | Bryan Newbold | 2018-09-10 | 7 | -61/+133 |
| | |||||
* | continue CRUD refactor, removing CUD handlers | Bryan Newbold | 2018-09-10 | 4 | -276/+60 |
| | | | | | | | | Can't remove the "get" handlers because of the expand parameter, which is only implemented for releases and in the handler (not in the CRUD trait, yet). Also didn't do the batch handler stuff yet. | ||||
* | squelch unused macro warning | Bryan Newbold | 2018-09-10 | 1 | -0/+2 |
| | |||||
* | database_entity_crud -> api_entity_crud | Bryan Newbold | 2018-09-10 | 5 | -5/+5 |
| | |||||
* | 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. |