| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
Manually resolve conflicts in:
rust/migrations/2018-05-12-001226_init/up.sql
|
| | |
|
| |
| |
| |
| |
| |
| | |
- use FatCatId much more often (though not everywhere yet)
- more consistent types
- remove redundant error handling code in wrappers
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This removes an entanglement between tests that was breaking on the
cockroachdb branch (where the database isn't reset between each
individual test).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As noted elsewhere, auto-increment sequences in postgres, mysql, and
cockroach can have gaps: when transactions that increment a number are
rolled back, a "gap" is left.
I didn't realize this, and it's problematic for the external changelog
API. I'll need to re-write the changelog inserter to query for the
current highest number when inserting, which is unfortunate and might
slow down bulk imports.
|
|\| |
|
| |
| |
| |
| | |
The per-row variant is for use with cockroach.
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| | |
Manually merged conflicts:
rust/migrations/2018-05-12-001226_init/up.sql
rust/src/api_server.rs
rust/src/database_schema.rs
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Started resolving conflicts in:
TODO
notes/cloud_instances.txt
rust/fatcat-api/README.md
rust/src/api_server.rs
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Need to review:
- changelog creation
- clobbering of existing editgroup flag
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
One failing test in this commit.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This does away entirely with the fancy CTE-based custom SQL inserts.
Because performance is currently only important for batch inserts, I
think this is acceptable, and will refactor to do batch inserts as
actual batch SQL operations next.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is the start of a large refactor to move all entity CRUD (create,
read, update, delete) model/database code into it's own file.
HACKING has been updated with an overview of what happens in each file.
Next steps:
- split rev (and sub-table) insertion in to db_rev_insert and make
create/update generic
- inserts should be batch (vector) by default
- move all other entities into this new trait framework
- bypass api_server wrappers and call into CRUD from api_wrappers for
entity ops (should be a big cleanup)
|
| | | |
|
| | |
| | |
| | |
| | | |
Other entities just stubs
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Basically reverts some big speedups around "single query inserts" (to
ident, rev, and edit tables concurrently), because cockroach doesn't
support "multiple uses of CTEs" (table expressions).
There's probably a way to rewrite using subqueries instead.
Also, would actually want to refactor and use NewRow structs instead of
tuples, I think.
|
| | |
|