Consider alternatives to custom genomic table

I think we should revisit the genomic table. I don't know if this was the best approach and think it was created to help with performance. We may want to consider looking into materialized view or other alternatives. I haven't put much thought into this, but wanted to create an issue to come back to later / see if people have thoughts

This issue is stale because it has been open 45 days with no activity. Please make a comment for triaging or closing the issue.

This issue is stale because it has been open 180 days with no activity. This issue will be closed if no further activity occurs in 14 days.

My questions here would be

if it's useful, maybe we can get it moved over to UTA proper
is it so useful that we need to be creating a whole new table/view/matview (which adds startup costs, hampers interoperability a bit, etc)? Can we just live with running some messy queries over existing tables?

Being removed in #465

Navigation Menu

Repository navigation

Consider alternatives to custom `genomic` table #285

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Consider alternatives to custom genomic table #285

Description

Activity

github-actions commented on Jul 2, 2024

github-actions commented on Dec 30, 2024

github-actions commented on Jun 30, 2025

jsstevenson commented on Apr 2, 2026

korikuzma commented on May 15, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Consider alternatives to custom `genomic` table #285