core/appview/db/ at f94aa9e1d24c78158a48cd46812632ab6442cf38 · tangled.org/core · Tangled

tangled.org / core

9

Monorepo for Tangled tangled.org

9

core / appview / db /

at f94aa9e1d24c78158a48cd46812632ab6442cf38 44 files

Seongmin Lee appview/db: more flexible tables 5mo ago

appview/db: more flexible tables migrate tables: `stars`, `reactions`, `follows`, `public_keys` Two major changes: 1. Remove autoincrement id for these tables. AUTOINCREMENT primary key does not help much for these tables and only introduces slice performance overhead. Use default `rowid` with non-autoincrement integer instead. 2. Remove unique constraints other than `(did, rkey)` We cannot block users creating non-unique atproto records. Appview needs to handle those properly. For example, if user unstar a repo, appview should delete all existing star records pointing to that repo. To allow this, remove all constraints other than `(did, rkey)`. Minor changes done while migrating tables: - rename `thread_at` in `reactions` to `subject_at` to match with other tables - follow common column names like `did` and `created` - allow self-follow (similar reason to 2nd major change. we should block it from service layer instead) Signed-off-by: Seongmin Lee <git@boltless.me>

5 months ago

appview/bsky: init module to fetch and store bsky posts on loadup fetches recent tangled posts for use on landing page Signed-off-by: oppiliappan <me@oppi.li>

4 months ago

collaborators.go

appview: fix issue/pr notifications being skipped Lewis: May this revision serve well! <lewis@tangled.org>

1 month ago

collaborators_null_rkey_test.go

appview: fix issue/pr notifications being skipped Lewis: May this revision serve well! <lewis@tangled.org>

1 month ago

appview: don't notify on replayed events Signed-off-by: Seongmin Lee <git@boltless.me>

1 month ago

appview/db: more flexible tables migrate tables: `stars`, `reactions`, `follows`, `public_keys` Two major changes: 1. Remove autoincrement id for these tables. AUTOINCREMENT primary key does not help much for these tables and only introduces slice performance overhead. Use default `rowid` with non-autoincrement integer instead. 2. Remove unique constraints other than `(did, rkey)` We cannot block users creating non-unique atproto records. Appview needs to handle those properly. For example, if user unstar a repo, appview should delete all existing star records pointing to that repo. To allow this, remove all constraints other than `(did, rkey)`. Minor changes done while migrating tables: - rename `thread_at` in `reactions` to `subject_at` to match with other tables - follow common column names like `did` and `created` - allow self-follow (similar reason to 2nd major change. we should block it from service layer instead) Signed-off-by: Seongmin Lee <git@boltless.me>

5 months ago

appview: associate users to commits by did Enables commit verification for users using a DID in place of an email address. <https://tangled.org/@tangled.org/core/issues/218> Signed-off-by: tjh <did:plc:65gha4t3avpfpzmvpbwovss7>

9 months ago

appview/db: add tables and queries for focus mode Signed-off-by: oppiliappan <me@oppi.li>

2 weeks ago

appview/db: more flexible tables migrate tables: `stars`, `reactions`, `follows`, `public_keys` Two major changes: 1. Remove autoincrement id for these tables. AUTOINCREMENT primary key does not help much for these tables and only introduces slice performance overhead. Use default `rowid` with non-autoincrement integer instead. 2. Remove unique constraints other than `(did, rkey)` We cannot block users creating non-unique atproto records. Appview needs to handle those properly. For example, if user unstar a repo, appview should delete all existing star records pointing to that repo. To allow this, remove all constraints other than `(did, rkey)`. Minor changes done while migrating tables: - rename `thread_at` in `reactions` to `subject_at` to match with other tables - follow common column names like `did` and `created` - allow self-follow (similar reason to 2nd major change. we should block it from service layer instead) Signed-off-by: Seongmin Lee <git@boltless.me>

5 months ago

appview: replace `IssueComment` to `Comment` Signed-off-by: Seongmin Lee <git@boltless.me>

6 months ago

appview: drop DbWrapper, move jetstream helpers onto *DB Lewis: May this revision serve well! <lewis@tangled.org>

2 months ago

knot_acl_native.go

appview/db: native knot membership queries Lewis: May this revision serve well! <lewis@tangled.org>

3 weeks ago

knot_acl_native_test.go

appview/db: native knot membership queries Lewis: May this revision serve well! <lewis@tangled.org>

3 weeks ago

orm: extract orm package from appview includes query and migration helpers Signed-off-by: oppiliappan <me@oppi.li>

6 months ago

appview: update appview repo_language cache when loading index page Updating only on `refUpdate` event is unstable. Signed-off-by: Seongmin Lee <git@boltless.me>

1 month ago

appview: oauth session cache, backoff on stuck migrations Lewis: May this revision serve well! <lewis@tangled.org>

1 month ago

appview/db: fix up nits with newsletter handlers Signed-off-by: oppiliappan <me@oppi.li>

2 months ago

notifications.go

appview/db: mark notifications as read upon page visit when visiting an issue or a pull, automatically mark any notifications related to that issue/pull as read. Signed-off-by: oppiliappan <me@oppi.li>

1 month ago

appview/db: use narrower query to get pipeline statuses we still ingest any and all pipeline statuses events. Signed-off-by: oppiliappan <me@oppi.li>

1 month ago

pipeline_test.go

appview/db: use narrower query to get pipeline statuses we still ingest any and all pipeline statuses events. Signed-off-by: oppiliappan <me@oppi.li>

1 month ago

appview: allow users to set their preferences for the punchcard being displayed Signed-off-by: Will Andrews <will7989@hotmail.com>

4 months ago

appview: move tx rollback logic out of `db.UpsertProfile()` Signed-off-by: Seongmin Lee <git@boltless.me>

5 months ago

profile_test.go

appview: ingest profile deletion Lewis: May this revision serve well! <lewis@tangled.org>

1 month ago

appview: allow pub key name updating from atproto ingestion Signed-off-by: Will Andrews <did:plc:dadhhalkfcq3gucaq25hjqon>

2 months ago

appview: replace `PullComment` to `Comment` Including db migration to migrate `issue_comments` and `pull_comments` to unified `comments` table. Signed-off-by: Seongmin Lee <git@boltless.me>

7 months ago

appview/db: fix off-by-1 in punchcard Date.YearDay produces an int in the range 1-365/366 but slices are indexed from 0. Signed-off-by: oppiliappan <me@oppi.li>

5 months ago

appview/db: more flexible tables migrate tables: `stars`, `reactions`, `follows`, `public_keys` Two major changes: 1. Remove autoincrement id for these tables. AUTOINCREMENT primary key does not help much for these tables and only introduces slice performance overhead. Use default `rowid` with non-autoincrement integer instead. 2. Remove unique constraints other than `(did, rkey)` We cannot block users creating non-unique atproto records. Appview needs to handle those properly. For example, if user unstar a repo, appview should delete all existing star records pointing to that repo. To allow this, remove all constraints other than `(did, rkey)`. Minor changes done while migrating tables: - rename `thread_at` in `reactions` to `subject_at` to match with other tables - follow common column names like `did` and `created` - allow self-follow (similar reason to 2nd major change. we should block it from service layer instead) Signed-off-by: Seongmin Lee <git@boltless.me>

5 months ago

appview/db: add db queries for recent links Signed-off-by: oppiliappan <me@oppi.li>

4 weeks ago

recents_test.go

appview/db: add db queries for recent links Signed-off-by: oppiliappan <me@oppi.li>

4 weeks ago

appview: use `#comment-{rkey}` instead of appview-local id Signed-off-by: Seongmin Lee <git@boltless.me>

1 month ago

registration.go

appview: kt+sp members ingestion Lewis: May this revision serve well! <lewis@tangled.org>

1 month ago

appview: fix issue/pr notifications being skipped Lewis: May this revision serve well! <lewis@tangled.org>

1 month ago

repos_rename_test.go

knotmirror,spindle,appview: propagate repo rename across services Lewis: May this revision serve well! <lewis@tangled.org>

2 months ago

appview: delete knot repos when its registration is removed Lewis: May this revision serve well! <lewis@tangled.org>

1 month ago

appview/db: allow regenerating invite codes users sometimes want to regenerate invite codes, but signups_inflight never replaces the old value, since the email column has a unique constraint. by using `or replace`, we can update the invite code. this keeps the db in sync with whatever the user sees in their inbox. Signed-off-by: oppiliappan <me@oppi.li>

4 months ago

site_deploys.go

appview/db: queries use repo_did lookups Lewis: May this revision serve well! <lewis@tangled.org>

2 months ago

appview/db: queries use repo_did lookups Lewis: May this revision serve well! <lewis@tangled.org>

2 months ago

appview: kt+sp members ingestion Lewis: May this revision serve well! <lewis@tangled.org>

1 month ago

appview/db: queries use repo_did lookups Lewis: May this revision serve well! <lewis@tangled.org>

2 months ago

orm: extract orm package from appview includes query and migration helpers Signed-off-by: oppiliappan <me@oppi.li>

6 months ago

appview/db: more flexible tables migrate tables: `stars`, `reactions`, `follows`, `public_keys` Two major changes: 1. Remove autoincrement id for these tables. AUTOINCREMENT primary key does not help much for these tables and only introduces slice performance overhead. Use default `rowid` with non-autoincrement integer instead. 2. Remove unique constraints other than `(did, rkey)` We cannot block users creating non-unique atproto records. Appview needs to handle those properly. For example, if user unstar a repo, appview should delete all existing star records pointing to that repo. To allow this, remove all constraints other than `(did, rkey)`. Minor changes done while migrating tables: - rename `thread_at` in `reactions` to `subject_at` to match with other tables - follow common column names like `did` and `created` - allow self-follow (similar reason to 2nd major change. we should block it from service layer instead) Signed-off-by: Seongmin Lee <git@boltless.me>

5 months ago

timeline_test.go

appview/db: more flexible tables migrate tables: `stars`, `reactions`, `follows`, `public_keys` Two major changes: 1. Remove autoincrement id for these tables. AUTOINCREMENT primary key does not help much for these tables and only introduces slice performance overhead. Use default `rowid` with non-autoincrement integer instead. 2. Remove unique constraints other than `(did, rkey)` We cannot block users creating non-unique atproto records. Appview needs to handle those properly. For example, if user unstar a repo, appview should delete all existing star records pointing to that repo. To allow this, remove all constraints other than `(did, rkey)`. Minor changes done while migrating tables: - rename `thread_at` in `reactions` to `subject_at` to match with other tables - follow common column names like `did` and `created` - allow self-follow (similar reason to 2nd major change. we should block it from service layer instead) Signed-off-by: Seongmin Lee <git@boltless.me>

5 months ago

appview/state: ingest knot ACL events into roster Lewis: May this revision serve well! <lewis@tangled.org>

1 week ago

appview/db: queries use repo_did lookups Lewis: May this revision serve well! <lewis@tangled.org>

2 months ago