7
3
Fork
You've already forked workflows
1

PostgreSQL in the Nix environment #3

Open
opened 2025年11月05日 01:43:12 +01:00 by ava · 0 comments
Owner
Copy link

PostgreSQL is a commonly used piece of software within the polyphony repositories. In the context of Rust, it is often depended upon by compile-time SQL validation checks.

The workflows repository should have an easy way of including a PostgreSQL database in the workspace environment, if needed. A working base can be found in the sonata repository, where the flake.nix and scripts/db.sh files together provide an easy way to interact with a PostgreSQL database. It would suffice if this solution were adapted slightly and added into this repository here.

PostgreSQL is a commonly used piece of software within the polyphony repositories. In the context of Rust, it is often depended upon by compile-time SQL validation checks. The workflows repository should have an easy way of including a PostgreSQL database in the workspace environment, if needed. A working base can be found in the [sonata repository](https://codeberg.org/polyphony/sonata), where the `flake.nix` and `scripts/db.sh` files together provide an easy way to interact with a PostgreSQL database. It would suffice if this solution were adapted slightly and added into this repository here.
ava changed title from (削除) PostgreSQL (削除ここまで) to PostgreSQL in the Nix environment 2025年11月05日 01:43:38 +01:00
Sign in to join this conversation.
No Branch/Tag specified
main
flori/improvements
No results found.
Labels
Clear labels
Compat/Breaking

Breaking change that won't be backward compatible
Difficulty
Easy

Measure of time-to-implement and cognitive complexity of the task. "Easy" tasks usually take 15-30min to complete. Likely suitable for first-time-contributors.
Difficulty
Hard

Measure of time-to-implement and cognitive complexity of the task. "Hard" tasks usually take 3h-15h to complete. Very likely not suitable for first-time-contributors.
Difficulty
Medium

Measure of time-to-implement and cognitive complexity of the task. "Medium" tasks usually take 30min-3h to complete. Likely not suitable for first-time-contributors.
Difficulty
Trivial

Measure of time-to-implement and cognitive complexity of the task. "Trivial" tasks usually take 1-15min to complete. Very likely suitable for first-time-contributors.
Difficulty
Very hard

Measure of time-to-implement and cognitive complexity of the task. "Hard" tasks usually take >15h to complete. Extremely unlikely to be suitable for first-time-contributors.
Good First Issue

This issue is a good task to take on if you are new to the project or the repository and looking to contribute.
Kind/Bug

Something is not working
Kind/Chore

Regular maintainance tasks, version bumps... things like that.
Kind/Documentation

Documentation changes
Kind/Enhancement

Improve existing functionality
Kind/Feature

New functionality
Kind
Meta

This issue is a collection of other, related issues.
Kind/Security

This is security issue
Kind/Testing

Issue or pull request related to testing
Priority
Critical

The priority is critical
Priority
High

The priority is high
Priority
Low

The priority is low
Priority
Medium

The priority is medium
Reviewed
Confirmed

Issue has been confirmed
Reviewed
Duplicate

This issue or pull request already exists
Reviewed
Invalid

Invalid issue
Reviewed
Won't Fix

This issue won't be fixed
Status
Abandoned

Somebody has started to work on this but abandoned work
Status
Blocked

Something is blocking this issue or pull request
Status
In Progress

This label is intended to be used when an outside collaborator is pursuing the completion of this issue, since they cannot be directly assigned to the task.
Status
Need More Info

Feedback is required to reproduce issue or to continue work
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
polyphony/workflows#3
Reference in a new issue
polyphony/workflows
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?