aboutsummaryrefslogtreecommitdiffstats
path: root/rust
Commit message (Collapse)AuthorAgeFilesLines
* fix isbn13 size check (!)Bryan Newbold2018-09-221-2/+2
|
* update export commandBryan Newbold2018-09-221-1/+1
|
* rustfmt, and implement schema tweaksBryan Newbold2018-09-226-105/+75
|
* container_name (not title), and shrink some BIGINTsBryan Newbold2018-09-221-4/+4
|
* codegen fatcat-api-specBryan Newbold2018-09-2210-2809/+2979
|
* squelch diesel macro warningsBryan Newbold2018-09-182-0/+4
|
* fatcat-export rustfmtBryan Newbold2018-09-171-28/+50
|
* re-generate database_schema.rsBryan Newbold2018-09-171-23/+23
|
* fix CHECK clausesBryan Newbold2018-09-173-22/+23
|
* 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
|
* remove is_not_null redundant lookup conditionsBryan Newbold2018-09-151-12/+0
|
* 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.
* remove duplicate response def from API specBryan Newbold2018-09-131-4/+0
|
* add missing fatcat-api-spec .gitignoreBryan Newbold2018-09-131-0/+2
|
* switch to new null (not \N) dump formatBryan Newbold2018-09-131-4/+4
|
* fix rust in-line tests, and parse_line takes refBryan Newbold2018-09-122-7/+7
| | | | Forgot to run tests before pushing... thanks CI!
* need to specify binary for 'cargo run' nowBryan Newbold2018-09-122-2/+2
|
* rust/TODO updateBryan Newbold2018-09-121-11/+1
|
* improvements to fatcat-export outputBryan Newbold2018-09-114-24/+136
|
* improvements to fatcat-exportBryan Newbold2018-09-113-29/+80
|
* use idiomatic from_str for ExpandFlagsBryan Newbold2018-09-112-14/+18
|
* more subtle local ident check in release.db_expand()Bryan Newbold2018-09-111-4/+4
|
* first pass fast exportBryan Newbold2018-09-114-1/+335
|
* implement new editgroup_id behaviorBryan Newbold2018-09-1113-249/+458
|
* refactor entity get and 'expansion'Bryan Newbold2018-09-113-81/+64
|
* derive PartialEq for FatCatIdBryan Newbold2018-09-111-1/+1
|
* add ExpandFlags typeBryan Newbold2018-09-111-0/+72
|
* finish fatcat-api => fatcat-api-spec refactorBryan Newbold2018-09-118-17/+17
|
* fix fatcat-api-spec depsBryan Newbold2018-09-112-6/+6
|
* new rustfmtBryan Newbold2018-09-112-26/+35
|
* refactor fatcat-api => fatcat-api-specBryan Newbold2018-09-1122-64/+109
|
* update TODO lists (september plan)Bryan Newbold2018-09-111-16/+31
|
* rust clippy (lint) tweaksBryan Newbold2018-09-114-14/+15
|
* use JSONB over JSONBryan Newbold2018-09-102-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 branchBryan Newbold2018-09-101-0/+2
|
* update TODOBryan Newbold2018-09-101-8/+2
|
* many small API cleanupsBryan Newbold2018-09-105-193/+148
| | | | | | - use FatCatId much more often (though not everywhere yet) - more consistent types - remove redundant error handling code in wrappers
* re-gen rust codeBryan Newbold2018-09-107-61/+133
|
* continue CRUD refactor, removing CUD handlersBryan Newbold2018-09-104-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 warningBryan Newbold2018-09-101-0/+2
|
* database_entity_crud -> api_entity_crudBryan Newbold2018-09-105-5/+5
|
* 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.
* generic edit accept, and per-row variantBryan Newbold2018-09-092-44/+158
| | | | The per-row variant is for use with cockroach.
* api_server: give up and use star schema importBryan Newbold2018-09-091-6/+1
|
* update TODOBryan Newbold2018-09-091-9/+11
|
* parallelize abstracts insertionBryan Newbold2018-09-091-15/+20
|
* TODO and commentBryan Newbold2018-09-072-1/+2
|
* fixes after autoaccept mergeBryan Newbold2018-09-074-49/+41
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-03 18:13:40 +0000