Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change db names #422

Closed
wants to merge 7 commits into from
Closed

Conversation

alneberg
Copy link
Member

An effort to standardise variable names that refers to a single specific StatusDB database.

In a few cases, I have dropped the option dbname to some classes, I've checked with taca-ngi-pipeline as well that these options were not used. Might need to check elsewhere as well if these classes are used there.

self.name_view = {k.key: k.id for k in self.db.view("names/name", reduce=False)}
self.proj_list = {
k.key: k.value
for k in self.db.view("names/project_ids_list", reduce=False)
for k in self.flowcells_db.view("names/project_ids_list", reduce=False)
if k.key
}


class X_FlowcellRunMetricsConnection(StatusdbSession):
def __init__(self, config, dbname="x_flowcells"):
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the dbname here used in taca_ngi_pipeline?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes you're right. It is reused in the common methods in the StatusDBSession class. Hmm, might have to rethink this.

@alneberg alneberg closed this Apr 19, 2024
@alneberg
Copy link
Member Author

Closing since it became a bit more complicated than I first hoped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants